devel September 2018

devel@lists.centos.org

24 participants
25 discussions

Rocky RDO Release Announcement
by Rain Leander 20 Sep '18

20 Sep '18

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2018/09/rdo-rocky-released/ --- The RDO community is pleased to announce the general availability of the RDO build for OpenStack Rocky for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Rocky is the 18th release from the OpenStack project, which is the work of more than 1400 contributors from around the world <http://stackalytics.com/>. The release already available on the CentOS mirror network at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-rocky/ The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG <https://wiki.centos.org/SpecialInterestGroup/Cloud>. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform <https://www.redhat.com/en/technologies/linux-platforms/openstack-platform>, is 100% open source, with all code changes going upstream first. ]4 <https://www.goodfreephotos.com/> Photo via Good Free Photos New and Improved Interesting things in the Rocky release include: - New neutron ML2 driver networking-ansible <https://networking-ansible.readthedocs.io/en/latest/> has been included in RDO. This module abstracts management and interaction with switching hardware to Ansible Networking. - Swift3 has been moved to swift package as the “s3api” middleware. Other improvements include: - Metalsmith <https://metalsmith.readthedocs.io/en/latest/> is now included in RDO. This is a simple tool to provision bare metal machines using ironic, glance and neutron. Contributors During the Rocky cycle, we saw the following new contributors: - Bob Fournier - Bogdan Dobrelya - Carlos Camacho - Carlos Goncalves - Cédric Jeanneret - Charles Short - Dan Smith - Dustin Schoenbrun - Florian Fuchs - Goutham Pacha Ravi - Ilya Etingof - Konrad Mosoń - Luka Peschke - mandreou - Nate Johnston - Sandhya Dasu - Sergii Golovatiuk - Tobias Urdin - Tony Breeds - Victoria Martinez de la Cruz - Yaakov Selkowitz Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all SIXTY-NINE contributors who participated in producing this release. This list includes commits to rdo-packages and rdo-infra repositories: - Ade Lee - Alan Bishop - Alan Pevec - Alex Schultz - Alfredo Moralejo - Bob Fournier - Bogdan Dobrelya - Brad P. Crochet - Carlos Camacho - Carlos Goncalves - Cédric Jeanneret - Chandan Kumar - Charles Short - Christian Schwede - Daniel Alvarez - Daniel Mellado - Dansmith - Dmitry Tantsur - Dougal Matthews - Dustin Schoenbrun - Emilien Macchi - Eric Harney - Florian Fuchs - Goutham Pacha Ravi - Haikel Guemar - Honza Pokorny - Ilya Etingof - James Slagle - Jason Joyce - Javier Peña - Jistr - Jlibosva - Jon Schlueter - Juan Antonio Osorio Robles - karthik s - Kashyap Chamarthy - Kevin Tibi - Konrad Mosoń - Lon - Luigi Toscano - Luka Peschke - marios - Martin André - Matthew Booth - Matthias Runge - Mehdi Abaakouk - Nate Johnston - Nmagnezi - Oliver Walsh - Pete Zaitcev - Pradeep Kilambi - rabi - Radomir Dopieralski - Ricardo Noriega - Sandhya Dasu - Sergii Golovatiuk - shrjoshi - Steve Baker - Thierry Vignaud - Tobias Urdin - Tom Barron - Tony Breeds - Tristan de Cacqueray - Victoria Martinez de la Cruz - Yaakov Selkowitz - yatin The Next Release Cycle At the end of one release, focus shifts immediately to the next, Stein <https://wiki.openstack.org/wiki/Release_Naming/S_Proposals> which has a slightly longer release cycle due to the PTG Summit co-location next year <https://ttx.re/future-of-ptg.html> with an estimated GA the week of 08-12 April 2019. The full schedule is available at https://releases.openstack.org/stein/schedule.html. Twice during each release cycle, RDO hosts official Test Days shortly after the first and third milestones; therefore, the upcoming test days are 01-02 November 2018 for Milestone One and 14-15 March 2019 for Milestone Three. Get Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation <https://www.rdoproject.org/install/packstack/>. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use the TripleO Quickstart <https://www.rdoproject.org/tripleo/> and you’ll be running a production cloud in short order. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program <https://www.openstack.org/passport>. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project participates in a Q&A service at https://ask.openstack.org. We also have our [users(a)lists.rdoproject.org[( https://lists.rdoproject.org/mailman/listinfo/users) for RDO-specific users and operrators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list <https://lists.rdoproject.org/mailman/listinfo/dev>. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org <https://lists.rdoproject.org/mailman/listinfo>. You can also find extensive documentation on RDOproject.org <https://www.rdoproject.org/>. The #rdo channel on Freenode IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS mailing lists <https://lists.centos.org/mailman/listinfo> and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages <https://www.rdoproject.org/contribute/>, peruse the CentOS Cloud SIG page <https://wiki.centos.org/SpecialInterestGroup/Cloud>, and inhale the RDO packaging documentation <https://www.rdoproject.org/documentation/rdo-packaging/>. Join us in #rdo on the Freenode IRC network and follow us on Twitter @RDOCommunity <http://twitter.com/rdocommunity/>. You can also find us on Facebook <https://facebook.com/rdocommunity>, Google+ <https://plus.google.com/communities/110409030763231732154> and YouTube <https://www.youtube.com/channel/UCWYIPZ4lm4P3_pzZ9Hx9awg>.

1 0

[OpsTools] Introduction & Joining Request
by Christian Gebler 20 Sep '18

20 Sep '18

Hello everyone, my name is Christian and I would like to be part of CentOS OpsTools SIG. I'm a sysadmin for about 15 years now with a main focus on web application hosting. Most of the time in a global IT environment and with the goal to keep the systems secure, highly available and on a good performance. I often had to use a linux distributions that the customer wanted to use, but in the last 5 years I am in the lucky position to mainly use CentOS. (-: I have read the SIG wiki page with great enthusiasm and want to contribute something useful to the group. So my questions are...how can I join the OpsTools SIG and how can I easily start to contribute something useful to the group? Thanks a lot! (-: - Chris

2 1

Doubt on mmap :kernel-3.10.0-693.11.6.el7
by Prem Kumar 19 Sep '18

19 Sep '18

We are trying to map the disk file and content is written in to specific offset. In meanwhile, if try to access the mmap'd content at specified offset, we are getting NULL value. we have not called msync() yet. the mmap called with MAP_SHARED. Is it possible that mmap content can differ on read after write or is this the problem happening because read is called before the msync(). Thanks, Prem

1 0

Authorization to use CentOS logo in GNOME Boxes
by Fabiano Fidêncio 19 Sep '18

19 Sep '18

People, Firstly, sorry for the cross-list post (centos-devel and centos-docs). I'd like to reach you in order to ask for a formal authorization to use CentOS logo on GNOME Boxes[0]. GNOME Boxes already shows a few other distro's logos as you can check here[1]. Would be possible to get the explicit confirmation that we could use CentOS logo as well? [0]: https://wiki.gnome.org/Apps/Boxes [1]: https://gitlab.gnome.org/GNOME/gnome-boxes/raw/master/README.logos Best Regards, -- Fabiano Fidêncio

4 5

Cancelling Today's CBS Meeting
by Brian Stinson 19 Sep '18

19 Sep '18

Hi Folks, We'll be cancelling today's CBS meeting. If there are topics to discuss in the meantime, please bring them here and we can handle things on-list or at next week's meeting. Cheers! --Brian

2 1

Reminder: CFP for FOSDEM Dojo is open
by Rich Bowen 14 Sep '18

14 Sep '18

The annual Dojo at FOSDEM - https://wiki.centos.org/Events/Dojo/Brussels2019 - will be happening on February 1st, 2019, at the Grand Place Marriott. The CFP is now open - https://goo.gl/forms/XkXbC2AZBgKvfDNF2 - and we intend to close it on October 15th, when I get to my desk in the morning, so don't put it off. See you in Brussels! --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Hurricane Florence and CentOS CI/CBS
by Brian Stinson 12 Sep '18

12 Sep '18

Hi All, Some of you may know that the CentOS Community Build System, and CentOS CI Infrastructures are hosted in Raleigh, North Carolina. I wanted to take this opportunity to let all of you know that outages are possible (but not expected) in the coming days as Hurricane Florence makes its way toward the US East coast. We are confident in the precautions taken by our datacenter vendor, and in the preparedness plans by our DC operations team. If there happen to be outages, we will work to get things back as soon as we can. Cheers! -- Brian Stinson CentOS Infrastructure Team

1 0

September newsletter
by Rich Bowen 10 Sep '18

10 Sep '18

The September newsletter has been published - https://blog.centos.org/2018/09/centos-pulse-newsletter-september-2018-1804/ You'll notice (if you make a habit of reading the newsletter) that this edition has moved from the wiki to the blog, for various reasons discussed over on the promo mailing list. I will begin drafting the October newsletter later today. If you'd like to participate in that process, please let me know, so that we can get you added to the editors list. blog.centos.org authenticates against your existing CentOS account, so you already have an account on there, we just need to add you to the right ACL. --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

[RFE] Distinguished volume ids between different kinds of ISOs
by Fabiano Fidêncio 10 Sep '18

10 Sep '18

The reasoning behind this request is to have more accurate data in osinfo-db that could be used, for instance, by GNOME Boxes and virt-manager. Currently, as the "Everything", "DVD", "Minimal" and "Network" ISOs have exactly the same Volume id (CentOS 7 x86_64) we can't distinguish the ISOs the user have in order to help them to properly pick up whatever is better for their needs. The way we have been currently working this around is by having the ISO's volume size (which are usually different) combined with their Volume id. This approach, however, won't work well in CentOS case as we're offering the "Rolling" ISOs to the users and their volume size will change on every new addition/removal. I've also noticed that for the Live ISOs they volume id is already distinguished (CentOS-7-x86_64-LiveKDE-* vs CentOS-7-x86_64-LiveGNOME-*) thus the RFE to see whether doing the same for the other ISOs would be something appealing to CentOS. This conversation can also be done in https://bugs.centos.org/view.php?id=15260 in case the developers prefer that way. Best Regards, -- Fabiano Fidêncio

1 0

HPC Sig
by Paul Graydon 06 Sep '18

06 Sep '18

Hi all, There was some email conversation on this list a couple of weeks ago about the HPC SIG, but it didn't really seem to go anywhere or have any solid conclusion, other than "join #centos-devel". Between some freenode instability/spam protections etc. some issues with my usual persistent session, and just sheer quantity of conversation happening there, it's somewhat hard to figure out where anything sits. I didn't see any obvious signs of further conversation there, but there's a good chance I missed it. If there was further conversation and someone would be able to point me towards it off list, I'd love to read it. As a cloud provider that provides high spec bare metal servers to customers, we're finding a lot of usage and interest from customers with various forms of HPC workloads, everything from GROMACs to Hadoop and beyond. CentOS, likewise, continues to be a popular distribution for our customers, across every hardware and virtual machine specification. If there's ideas on how to make HPC better on CentOS, I'd love to be part of the conversation, and see if there are opportunities to help. Paul

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2018