September 2018 - dev - Rdo List Archives

RDO Registry SSL certificate renewal on Mon, Oct 1

by Javier Pena

Hi all, We need to renew the RDO Registry SSL certificate. The process to do so is automated, but slightly more complex than the usual for an Apache web server. We will renew the certificate next Monday, October 1st. The estimated downtime is very short (< 10 minutes), but just take it into account if any CI jobs fail. Regards, Javier

6 years, 1 month

1
0
0 / 0

Status of python3 support in RDO Trunk Stein (25-sep)

by Alfredo Moralejo Alonso

Hi, One of the goals in RDO during Stein cycle is to get the RPM packages ready for python3. To get this done we are working in several actions in RDO project: 1. Update packages specs in RDO distgits to provide python3 packages when building in fedora builder [1]. This is WIP, some info about how to implement it and the current status can be found in [2]. I'd encourage package maintainers to review the python3 conversion related reviews (we are using py3-enable topic) for their packages or send reviews to update them in case it's not converted yet. Note that we are adding some new macros to make specs compatible with python2 (for CentOS 7 builders) and python3 (for fedora builder) that we will need to use until we can get rid of python2 packages. This will have some impact when adding new dependencies to the specs (make sure you use %{pyver} if you are updating an already converted spec) and when backporting changes from rpm-master to previous branches (may need to update patches to adapt them to the pre-py3 specs). 2. Add support for new services in puppet-openstack-integration scenarios using python3 on fedora 28 based stabilized repository. Once new services are added to python3 fedora DLRN builder, we will add them to the python3 p-o-i scenarios to make sure they keep working over time. If you have any doubt about this topic, don't hesitate to contact us using #rdo channel in freenode or using this mailing list. Best regards, Alfredo [1] https://trunk.rdoproject.org/fedora/report.html [2] https://review.rdoproject.org/etherpad/p/py3_conversion_status

6 years, 1 month

1
0
0 / 0

Upcoming Meetups

by Rain Leander

The following are the meetups I'm aware of over the next two weeks where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/events If there's a meetup in your area, it'd be super keen if you attended, took a few pictures and especially wrote up a summary of what was covered. And, as always, if you give me enough notice, I can send swag along with you. ~Rain. * Tuesday September 25 in Palo Alto, CA, US: Container Security Reality Check: Kubernetes and Beyond - https://www.meetup.com/openstack/events/254432089/ * Thursday September 27 in Dallas, TX, US: Dallas Kubernetes meetup: September. Openstack + K8s. Istio Service mesh. - https://www.meetup.com/Dallas-Kubernetes-Meetup/events/254585965/ * Thursday September 27 in Lyon, FR: OpenStack Rhône-Alpes Meet-up #8 - https://www.meetup.com/OpenStack-Rhone-Alpes/events/254234192/ * Thursday October 04 in Bucharest, RO: OpenStack Romania Meetup - October 2018 meetup - https://www.meetup.com/OpenStack-Bucharest-Romania-Meetup/events/254813224/ * Saturday October 06 in Littleton, CO, US: A Gentle, Hands-on Introduction to OpenStack with David L. Willson - https://www.meetup.com/sofreeus/events/254583920/ -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

6 years, 1 month

1
0
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-09-26 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/8759/

6 years, 1 month

1
0
0 / 0

Rocky RDO Release Announcement

by Rain Leander

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>.

6 years, 1 month

1
0
0 / 0

Upcoming Meetups

by Rain Leander

The following are the meetups I'm aware of over the next two weeks where OpenStack and/or RDO enthusiasts are likely to be present. If you know of others, please let me know, and/or add them to http://rdoproject.org/events If there's a meetup in your area, it'd be super keen if you attended, took a few pictures and especially wrote up a summary of what was covered. And, as always, if you give me enough notice, I can send swag along with you. ~Rain. * Tuesday September 25 in Palo Alto, CA, US: Container Security Reality Check: Kubernetes and Beyond - https://www.meetup.com/openstack/events/254432089/ * Thursday September 27 in Dallas, TX, US: Dallas Kubernetes meetup: September. Openstack + K8s. Istio Service mesh. - https://www.meetup.com/Dallas-Kubernetes-Meetup/events/254585965/ * Thursday September 27 in Lyon, FR: OpenStack Rhône-Alpes Meet-up #8 - https://www.meetup.com/OpenStack-Rhone-Alpes/events/254234192/

6 years, 1 month

1
0
0 / 0

Re: [rdo-dev] [rdo-users] [tripleo] Neutron external bridge setting

by Dan Sneddon

On Wed, Sep 19, 2018 at 10:13 AM Cody <codeology.lab(a)gmail.com> wrote: > Hi there, > > I sent a similar question below to OpenStack ML last week, but haven't > got any answers yet. Since it is a TripleO related question, I am > reposting it here and hope for a better luck. > > According to the TripleO documentation [1], the default Neutron > external bridge (NeutronExternalNetworkBridge) is left empty. This > seems to let the physical interface map to br-int instead of br-ex, > and (somehow) use more CPU power as oppose to using br-ex directly. I > don't get it... Does it mean the external traffic would go directly > from br-int to the physical interface without using br-ex? Could > someone walk me through the traffic flow in this case? I really > appreciate your help! > > [1] > https://docs.openstack.org/tripleo-docs/latest/install/advanced_deploymen... > > > Regards, > Cody > _______________________________________________ > users mailing list > users(a)lists.rdoproject.org > http://lists.rdoproject.org/mailman/listinfo/users > > To unsubscribe: users-unsubscribe(a)lists.rdoproject.org > If you set the Neutron external bridge explicitly (such as to "br-ex"), then only that bridge can be used for floating IPs and SNAT. This is because the router net namespace is attached directly to the external bridge, rather than to br-int. If you set this to a blank string, then everything will be tied to br-int, and you can have multiple external bridges, or multiple provider external networks on the same bridge. This is useful for separating floating IP pools for different tenants, or for other fine-grained traffic control. While it is true that setting this to a blank string means one extra bridge hop in the data path (from the router namespace to br-int), this is no longer such an issue as the OVS code is significantly more efficient than it used to be. Keep in mind that traffic will traverse several bridges before hitting the VM even in the case of using an explicit external bridge, so it's not like the one extra bridge hop doubles OVS CPU utilization, it's just a small fractional increase. I have always recommend that a blank string be used in all cases, as this leaves flexibility to add bridge interfaces in the future, and has an overall small impact on CPU utilization. In fact, setting an explicit external bridge was deprecated, and if it hasn't been removed by now I'm surprised. https://bugs.launchpad.net/neutron/+bug/1511578 -- Dan Sneddon | Senior Principal OpenStack Engineer dsneddon(a)redhat.com | redhat.com/openstack dsneddon:irc | @dxs:twitter

6 years, 2 months

2
1
0 / 0

Re: [rdo-dev] [rdo-users] [tripleo] Neutron external bridge setting

by Paul Yates

Hi Cody, Firstly, I don't work for the Openstack team. I'm with Red Hat Openshift, but I've worked with Openstack in the past and still have an interest in it and follow some of the mailing lists. >From past experience, and from what I take from the docs you linked is: Older versions of Openstack have the integration bridge (br-int) which routes traffic to the external bridge (br-ex) and traffic then flows through the physical interface. But this limits you to a single floating IP range. So, newer versions of Openstack set the external bridge setting as empty by default ( NeutronExternalNetworkBridge: "''" ). This allows you the capability of mapping multiple physical interfaces (bonded interfaces or trunked vlans) directly. While this method removes the ex-br, you are still introducing an overhead as you are routing multiple networks over one or more physical interfaces - hence the additional CPU usage. What the docs are saying is, if you intend to use multiple external networks (multiple floating IP rages) then leave this empty (as by default): NeutronExternalNetworkBridge: "''" But if you are only intending to use one external network (one floating IP range), then revert back to the old way of mapping the network to br-ex - otherwise, you are introducing an additional unnecessary overhead that you are not making use of. hope this helps. kind regards, On Wed, Sep 19, 2018 at 6:13 PM, Cody <codeology.lab(a)gmail.com> wrote: > Hi there, > > I sent a similar question below to OpenStack ML last week, but haven't > got any answers yet. Since it is a TripleO related question, I am > reposting it here and hope for a better luck. > > According to the TripleO documentation [1], the default Neutron > external bridge (NeutronExternalNetworkBridge) is left empty. This > seems to let the physical interface map to br-int instead of br-ex, > and (somehow) use more CPU power as oppose to using br-ex directly. I > don't get it... Does it mean the external traffic would go directly > from br-int to the physical interface without using br-ex? Could > someone walk me through the traffic flow in this case? I really > appreciate your help! > > [1] https://docs.openstack.org/tripleo-docs/latest/install/ > advanced_deployment/network_isolation.html#using-the- > native-vlan-for-floating-ips > > > Regards, > Cody > _______________________________________________ > users mailing list > users(a)lists.rdoproject.org > http://lists.rdoproject.org/mailman/listinfo/users > > To unsubscribe: users-unsubscribe(a)lists.rdoproject.org > -- Paul Yates Red Hat, Communications House, Cork Road, Waterford, Ireland. phone: +353 51 810166 <%2B420%20532294734> Email: pyates(a)redhat.com <lsvobodo(a)redhat.com>

6 years, 2 months

1
0
0 / 0

[meeting] RDO meeting (2018-09-19) minutes

by Javier Pena

============================== #rdo: RDO meeting - 2018-09-19 ============================== Meeting started by jpena at 15:02:05 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_09_19/2018/rdo... . Meeting summary --------------- * roll call (jpena, 15:02:23) * Status of python3 conversion (jpena, 15:06:34) * clients and libraries need to be python3 only in fedora30 so the must be converted to single python3 subpackage too (amoralej, 15:29:46) * next week's chair (jpena, 15:31:31) * ACTION: amoralej to chair the next meeting (jpena, 15:32:05) * open floor (jpena, 15:32:08) * LINK: https://blogs.rdoproject.org/2018/03/rdo-queens-released/ (leanderthal, 15:42:34) * LINK: https://etherpad.openstack.org/p/rdo-rocky-release (leanderthal, 15:47:45) * ACTION: jpena to try and fix repoxplorer new contributor stats, else poke fbo (jpena, 15:48:11) Meeting ended at 15:54:58 UTC. Action items, by person ----------------------- * amoralej * amoralej to chair the next meeting * jpena * jpena to try and fix repoxplorer new contributor stats, else poke fbo People present (lines said) --------------------------- * amoralej (72) * jpena (29) * leanderthal (24) * ykarel (21) * openstack (8) * PagliaccisCloud (3) * rdogerrit (1) * chkumar|ruck (1) Generated by `MeetBot`_ 0.1.4

6 years, 2 months

1
0
0 / 0

[Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2018-09-19 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/8759/

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev September 2018