devel

devel@lists.centos.org

8 participants
4617 discussions

Re: [CentOS-devel] Kernel Panic: CentOS 7.4
by Trevor Hemsley 05 Nov '19

05 Nov '19

Looking at kernel bugs on bugs.centos.org is not very useful. CentOS does not make code changes, it only rebuilds packages that are released for RHEL and publishes them. We really have no idea what code changes have been made by Red Hat. The current CentOS 7.7 kernel is 3.10.0-1062.4.1.el7.x86_64 and there are over 32,000 entries in `rpm -q --changelog kernel-3.10.0-1062.4.1.el7.x86_64` before you reach any mention of the 3.10.0-693.* 7.4-series kernels. That's 32,000 potential bugs that could have fixed your problem. If someone who had that problem had updated to a newer kernel and reported it as fixed then we would probably have closed that bug. Since no-one has, that either means they didn't care enough to update the bug report or no-one has tested it or it's not fixed. It would appear that you'll be the one to find out... Trevor On 05/11/2019 18:57, sumit gambhir wrote: > https://bugs.centos.org/view.php?id=14265#history. is still in the > open state. > Or Is it fixed in CentOS 7.7? > > On Wed, Nov 6, 2019 at 12:20 AM Trevor Hemsley > <trevor.hemsley(a)ntlworld.com <mailto:trevor.hemsley@ntlworld.com>> wrote: > > Run `yum update`. You are more than 2 years out of date. > > Only the current version - 7.7 at present - is supported, any > other version, the answer is update. > > Trevor > > On 05/11/2019 18:20, sumit gambhir wrote: >> >> There was a power cycle during the upgrade. >> >> We got following trace during kernel panic. >> >> Cannot login after software upgrade – system initializing message >> on Portal; on cli login prompt is seen following messages: >> >> >> System crashing due to >> [ 8780.678167] Hardware name: Cisco Systems, Inc. >> ENCS5412/K9/ENCS5412/K9, BIOS ENCS54_2.7.020620190951 02/06/2019 >> [ 8780.800565] Workqueue: events flush_to_ldisc >> [ 8780.853390] task: ffff9707f4bf30c0 ti: ffff9707f4448000 >> task.ti: ffff9707f4448000 >> [ 8780.944588] RIP: 0010:[<ffffffff83874b73>] >> [<ffffffff83874b73>] uart_write_room+0x13/0x50 >> [ 8781.045274] RSP: 0018:ffff9707f444bc60 EFLAGS: 00010286 >> [ 8781.110468] RAX: 0000000000000800 RBX: 000000000000000a RCX: >> ffff9707f444bfd8 >> [ 8781.197509] RDX: ffffffff83874b60 RSI: ffff970ed8206c00 RDI: >> ffff970ed8205000 >> [ 8781.284540] RBP: ffff9707f444bc70 R08: ffff970ec1e6ec00 R09: >> a3c427ffdbc3c000 >> [ 8781.371561] R10: a3c427ffdbc3c000 R11: 0000000000000001 R12: >> 0000000000000000 >> [ 8781.458579] R13: ffff970ed8205000 R14: ffff970ed8206c00 R15: >> ffff970ec1e6ecf6 >> [ 8781.545589] FS: 0000000000000000(0000) >> GS:ffff970edf000000(0000) knlGS:0000000000000000 >> [ 8781.644060] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> [ 8781.714429] CR2: 0000000000000150 CR3: 000000085b2be000 CR4: >> 00000000003607f0 >> [ 8781.801442] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> 0000000000000000 >> [ 8781.888437] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: >> 0000000000000400 >> [ 8781.975407] Call Trace: >> [ 8782.006205] [<ffffffff8385c730>] tty_write_room+0x20/0x30 >> [ 8782.073406] [<ffffffff8385966e>] process_echoes+0x6e/0x2e0 >> [ 8782.141642] [<ffffffff83b65e92>] ? mutex_lock+0x12/0x2f >> [ 8782.206744] [<ffffffff8385c14c>] n_tty_receive_char+0xd4c/0xe30 >> [ 8782.280188] [<ffffffff8385c3dc>] n_tty_receive_buf+0x1ac/0x470 >> [ 8782.352569] [<ffffffff8385f1ff>] flush_to_ldisc+0x10f/0x160 >> [ 8782.421832] [<ffffffff834b9d4f>] process_one_work+0x17f/0x440 >> [ 8782.493188] [<ffffffff834bade6>] worker_thread+0x126/0x3c0 >> [ 8782.561412] [<ffffffff834bacc0>] ? >> manage_workers.isra.25+0x2a0/0x2a0 >> [ 8782.641074] [<ffffffff834c1c31>] kthread+0xd1/0xe0 >> [ 8782.700887] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 >> [ 8782.775363] [<ffffffff83b74c37>] >> ret_from_fork_nospec_begin+0x21/0x21 >> [ 8782.855038] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 >> [ 8782.929516] Code: 01 00 00 81 e3 ff 0f 00 00 e8 0a 56 2f 00 89 >> d8 5b 41 5c 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 4c >> 8b a7 18 02 00 00 <49> 8b bc 24 50 01 00 00 e8 50 59 2f 00 41 8b >> 9c 24 48 01 00 00 >> [ 8783.165634] RIP [<ffffffff83874b73>] uart_write_room+0x13/0x50 >> [ 8783.238184] RSP <ffff9707f444bc60> >> [ 8783.281471] CR2: 0000000000000150 >> >> >> >> >> >> While going through the list of cases on centos, we found this >> similar case - https://bugs.centos.org/view.php?id=14265#history. >> However, there has been no activity on it since long. >> >> Can you please help us out to find out if there is an ongoing fix >> for it? >> >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel(a)centos.org <mailto:CentOS-devel@centos.org> >> https://lists.centos.org/mailman/listinfo/centos-devel >

1 0

Kernel Panic: CentOS 7.4
by sumit gambhir 05 Nov '19

05 Nov '19

There was a power cycle during the upgrade. We got following trace during kernel panic. Cannot login after software upgrade – system initializing message on Portal; on cli login prompt is seen following messages: System crashing due to [ 8780.678167] Hardware name: Cisco Systems, Inc. ENCS5412/K9/ENCS5412/K9, BIOS ENCS54_2.7.020620190951 02/06/2019 [ 8780.800565] Workqueue: events flush_to_ldisc [ 8780.853390] task: ffff9707f4bf30c0 ti: ffff9707f4448000 task.ti: ffff9707f4448000 [ 8780.944588] RIP: 0010:[<ffffffff83874b73>] [<ffffffff83874b73>] uart_write_room+0x13/0x50 [ 8781.045274] RSP: 0018:ffff9707f444bc60 EFLAGS: 00010286 [ 8781.110468] RAX: 0000000000000800 RBX: 000000000000000a RCX: ffff9707f444bfd8 [ 8781.197509] RDX: ffffffff83874b60 RSI: ffff970ed8206c00 RDI: ffff970ed8205000 [ 8781.284540] RBP: ffff9707f444bc70 R08: ffff970ec1e6ec00 R09: a3c427ffdbc3c000 [ 8781.371561] R10: a3c427ffdbc3c000 R11: 0000000000000001 R12: 0000000000000000 [ 8781.458579] R13: ffff970ed8205000 R14: ffff970ed8206c00 R15: ffff970ec1e6ecf6 [ 8781.545589] FS: 0000000000000000(0000) GS:ffff970edf000000(0000) knlGS:0000000000000000 [ 8781.644060] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8781.714429] CR2: 0000000000000150 CR3: 000000085b2be000 CR4: 00000000003607f0 [ 8781.801442] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 8781.888437] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 8781.975407] Call Trace: [ 8782.006205] [<ffffffff8385c730>] tty_write_room+0x20/0x30 [ 8782.073406] [<ffffffff8385966e>] process_echoes+0x6e/0x2e0 [ 8782.141642] [<ffffffff83b65e92>] ? mutex_lock+0x12/0x2f [ 8782.206744] [<ffffffff8385c14c>] n_tty_receive_char+0xd4c/0xe30 [ 8782.280188] [<ffffffff8385c3dc>] n_tty_receive_buf+0x1ac/0x470 [ 8782.352569] [<ffffffff8385f1ff>] flush_to_ldisc+0x10f/0x160 [ 8782.421832] [<ffffffff834b9d4f>] process_one_work+0x17f/0x440 [ 8782.493188] [<ffffffff834bade6>] worker_thread+0x126/0x3c0 [ 8782.561412] [<ffffffff834bacc0>] ? manage_workers.isra.25+0x2a0/0x2a0 [ 8782.641074] [<ffffffff834c1c31>] kthread+0xd1/0xe0 [ 8782.700887] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 [ 8782.775363] [<ffffffff83b74c37>] ret_from_fork_nospec_begin+0x21/0x21 [ 8782.855038] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40 [ 8782.929516] Code: 01 00 00 81 e3 ff 0f 00 00 e8 0a 56 2f 00 89 d8 5b 41 5c 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 4c 8b a7 18 02 00 00 <49> 8b bc 24 50 01 00 00 e8 50 59 2f 00 41 8b 9c 24 48 01 00 00 [ 8783.165634] RIP [<ffffffff83874b73>] uart_write_room+0x13/0x50 [ 8783.238184] RSP <ffff9707f444bc60> [ 8783.281471] CR2: 0000000000000150 While going through the list of cases on centos, we found this similar case - https://bugs.centos.org/view.php?id=14265#history. However, there has been no activity on it since long. Can you please help us out to find out if there is an ongoing fix for it?

2 1

CentOS Storage SIG monthly meeting minutes
by Niels de Vos 05 Nov '19

05 Nov '19

We have decided to pickup the regular CentOS Storage SIG meetings again. The meeting will take place on the first Tuesday of every month at 10:00 UTC in #centos-meeting on Freenode IRC. Today was our first (unannounced) meeting of the series. Cheers, Niels Minutes: https://www.centos.org/minutes/2019/November/centos-meeting.2019-11-05-10.0… Minutes (text): https://www.centos.org/minutes/2019/November/centos-meeting.2019-11-05-10.0… Log: https://www.centos.org/minutes/2019/November/centos-meeting.2019-11-05-10.0… ======================================================== #centos-meeting: CentOS Storage SIG meeting (2019-11-05) ======================================================== Meeting started by ndevos at 10:03:14 UTC. The full logs are available at https://www.centos.org/minutes/2019/November/centos-meeting.2019-11-05-10.0… . Meeting summary --------------- * Meeting time update (ndevos, 10:07:10) * ACTION: rbowen to find out how to update https://centos.org/community/calendar/ (ndevos, 10:09:54) * Updates not available on mirrors yet (ndevos, 10:10:24) * ACTION: kbsingh to look into cause of delay signing+pushing contents to mirror.c.o (ndevos, 10:14:52) * Open Floor \o/ (ndevos, 10:15:04) Meeting ended at 11:04:10 UTC. Action Items ------------ * rbowen to find out how to update https://centos.org/community/calendar/ * kbsingh to look into cause of delay signing+pushing contents to mirror.c.o Action Items, by person ----------------------- * **UNASSIGNED** * rbowen to find out how to update https://centos.org/community/calendar/ * kbsingh to look into cause of delay signing+pushing contents to mirror.c.o People Present (lines said) --------------------------- * ndevos (21) * Arrfab (4) * centbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

rpm2cpi and Mock on CentOS 7 and 8 cannot handle Fedora 31 SRPM's
by Nico Kadel-Garcia 03 Nov '19

03 Nov '19

Fedora 31 elected to use a new compression algorithm, "zstd", to compress RPM's. The result of this unnecessary optimization is that even commercially supported and long-term-support operating systems, like RHEL 7 and 8, and CentOS 7 and 8, cannot deconstruct leading edge Fedora SRPM's, especially the bleeding edge ones from rawhide. This creates a real backporting problem for people like me who publish internal backports of leading edge components, or who try to publish backports from Fedora to EPEL. It breaks the "mock" toolkit for compiling RPMs under various new operating systems, and it breaks the bility to run "rpmbuild" on a Fedora 31 SRPM. Whether I consider zstd to be an extraneous and entirely unnecessary optimization, it's in place. There are support problems of CentOS taking on supporting an enhanced RPM software to resolve this. Is there any interest in taking this on for centosplus?

4 10

CPE Weekly: 2019-11-01
by Aoife Moloney 01 Nov '19

01 Nov '19

Hi everyone, Welcome to the CPE team weekly project update mail! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. For increased communication between our communities, we have created #redhat-cpe on Freenode! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. Note: This document is currently built from individual reports rolled into a google document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. High Level Project Updates: CentOS: Cbs.centos.org migration Started planning for how to make community builds available with EL8 Deploying a new koji host that will be used for cbs.centos.org migration Migrated following services from puppet configuration management: https://feeds.centos.org (now under ansible, covering CentOS Stream/8) https://planet.centos.org (now under ansible) Continuing conversion of further puppet roles to ansible CentOS CI Added CentOS 8 and CentOS Stream in cico Updated python-cicoclient to support CentOS 8 and CentOS Stream Fedora: F31 was released on Tuesday 29th October! https://fedoramagazine.org/announcing-fedora-31/ F31 documentation was also released. Fedora 31 websites had a harder release, but it is clearer to parties involved the amount of work which was done in the background every release. Fedora Infrastructure freeze ended and so changes to infrastructure can occur until the F32 Beta in about 3 months. Congratulations to everyone in the Community whom were involved with the release, onwards to F32 :) Rawhide Gating: A call to arms email has been sent asking for testers for multi build https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Single build workflow is working again and is aligned with multi-build workflows also https://bodhi.stg.fedoraproject.org/updates/FEDORA-2019-3d6e95211e Update for the multi-build workflow needs to be created with autotime on, otherwise the update will not get pushed https://bodhi.stg.fedoraproject.org/updates/FEDORA-2019-90b8bce568 Overview page of the remaining blockers and dependencies organized at: https://hackmd.io/Gbuu9JOPR--Y2yNCBEYI5A?view Ci.centos.org is still not using fedora-messaging Ci-resultsdb-listener with fedora-messaging and support for the new messages format is not deployed in production yet repoSpanner Developed another experimental patch that got us an ~83x speed up. Got 122% performance patch merged. Worked with smooge to get a repoSpanner cluster deployed on realistic cross-datacenter hardware. repoSpanner is still extremely slow when all three DCs are used. Est. 58 minutes to push Bodhi into it, even with the 83x speedup patch. The team is investigating a solution. Application Retirements Elections: Blocking issue was fixed https://pagure.io/fedora-infrastructure/issue/8253 Fedocal : jlanda started to work on communishift port https://pagure.io/fedora-infrastructure/issue/8274 Nuancier: Benson Muite is now working on OIDC authentication - Thank you Benson! Fed-msg: fedmsg-logger equivalent for fedora-messaging https://pagure.io/releng/pull-request/8940 Comments? Suggestions? Feedback? Let Us Know! Have a lovely weekend! Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

Join us in #redhat-cpe on Freenode
by Leigh Griffin 01 Nov '19

01 Nov '19

This is originally from Randy Barlow but for time zone reasons I am forwarding this onto the devel list as we will reference it in our weekly update. Thanks Randy for putting this together :) ---- This is a repost from https://blog.electronsweatshop.com/join-us-in-redhat-cpe-on-freenode.html tl;dr; join us in #redhat-cpe on Freenode! Many moons ago, Red Hat merged the CentOS infrastructure team with the Fedora Infrastructure team, into a team known as "Community Platform Engineering" (CPE). Most of the individuals on the combined team have mostly continued to focus on the project they were assigned to before the merger, but as time has gone by we have looked for opportunities to collaborate more. I recently observed that we had been using internal communications to communicate about collaborative projects between CentOS and Fedora infrastructures, rather than public forums. This happened mostly because we've long had internal methods for communicating, and because the collaboration is not particular to either community, so using #fedora-admin on Freenode didn't seem particularly proper either, for example. Thus, this week we have established the #redhat-cpe channel on Freenode as a place for our team to communicate openly about the collaborative efforts we are engaged in. Join us there if you are interested in helping us bring CentOS and Fedora closer together! -- Leigh Griffin Engineering Manager Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City lgriffin(a)redhat.com M: +353877545162 IM: lgriffin @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig>

2 2

Buildlogs Push
by kbsingh＠centos.org 31 Oct '19

31 Oct '19

N: 7/virt/x86_64/container/ buildah-1.11.4-3.el7.x86_64.rpm

7 9

Buildlogs Push
by kbsingh＠centos.org 31 Oct '19

31 Oct '19

N: 7/cloud/x86_64/openstack-train/ ansible-role-network-runner-0.1.7-3.el7.noarch.rpm N: 7/cloud/x86_64/openstack-train/ python2-network-runner-0.1.7-3.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ ansible-role-network-runner-0.1.7-3.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ python2-network-runner-0.1.7-3.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ ansible-role-network-runner-0.1.7-3.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ python2-network-runner-0.1.7-3.el7.noarch.rpm

1 0

[CloudSIG] Train RDO Release Announcement
by Rain Leander 31 Oct '19

31 Oct '19

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2019/10/rdo-train-released/ --- The RDO community is pleased to announce the general availability of the RDO build for OpenStack Train for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Train is the 20th release from the OpenStack project, which is the work of more than 1115 contributors <https://www.stackalytics.com/?metric=commits> from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-train/. While we normally also have the release available via http://mirror.centos.org/altarch/7/cloud/ppc64le/ and http://mirror.centos.org/altarch/7/cloud/aarch64/ – there have been issues with the mirror network which is currently being addressed via https://bugs.centos.org/view.php?id=16590. <http://mirror.centos.org/altarch/7/cloud/aarch64/> 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. 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, is 100% open source, with all code changes going upstream first. PLEASE NOTE: At this time, RDO Train provides packages for CentOS7 only. We plan to move RDO to use CentOS8 as soon as possible during Ussuri development cycle so Train will be the last release working on CentOS7. *Interesting things in the Train release include:* - Openstack Ansible <https://docs.openstack.org/openstack-ansible/latest/>, which provides ansible playbooks and roles for deployment, added murano <https://docs.openstack.org/murano/latest/> support and fully migrated to systemd-journald from rsyslog. This project makes deploying OpenStack from source in a way that makes it scalable while also being simple to operate, upgrade, and grow. - Ironic <https://wiki.openstack.org/wiki/Ironic>, the Bare Metal service, aims to produce an OpenStack service and associated libraries capable of managing and provisioning physical machines in a security-aware and fault-tolerant manner. Beyond providing basic support for building software RAID and a myriad of other highlights, this project now offers a new tool for building ramdisk images, ironic-python-agent-builder <https://docs.openstack.org/ironic-python-agent-builder/latest/>. *Other improvements include:* - Tobiko <https://tobiko.readthedocs.io/en/latest/> is now available within RDO! This project is an OpenStack testing framework focusing on areas mostly complementary to Tempest <https://docs.openstack.org/tempest/latest/>. While the tempest main focus has been testing OpenStack rest APIs, the main Tobiko focus would be to test OpenStack system operations while “simulating” the use of the cloud as the final user would. Tobiko’s test cases populate the cloud with workloads such as instances, allows the CI workflow to perform an operation such as an update or upgrade, and then runs test cases to validate that the cloud workloads are still functional. - Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/train/highlights.html. <https://releases.openstack.org/train/highlights.html> *Contributors* During the Train cycle, we saw the following new RDO contributors: - Joel Capitao - Zoltan Caplovic - Sorin Sbarnea - Sławek Kapłoński - Damien Ciabrini - Beagles - Soniya Vyas - Kevin Carter (cloudnull) - fpantano - Michał Dulko - Stephen Finucane - Sofer Athlan-Guyot - Gauvain Pocentek - John Fulton - Pete Zaitcev 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 65 contributors who participated in producing this release. This list includes commits to rdo-packages and rdo-infra repositories: - Adam Kimball - Alan Bishop - Alex Schultz - Alfredo Moralejo - Arx Cruz - Beagles - Bernard Cafarelli - Bogdan Dobrelya - Brian Rosmaita - Carlos Goncalves - Cédric Jeanneret - Chandan Kumar - Damien Ciabrini - Daniel Alvarez - David Moreau Simard - Dmitry Tantsur - Emilien Macchi - Eric Harney - fpantano - Gael Chamoulaud - Gauvain Pocentek - Jakub Libosvar - James Slagle - Javier Peña - Joel Capitao - John Fulton - Jon Schlueter - Kashyap Chamarthy - Kevin Carter (cloudnull) - Lee Yarwood - Lon Hohberger - Luigi Toscano - Luka Peschke - marios - Martin Kopec - Martin Mágr - Matthias Runge - Michael Turek - Michał Dulko - Michele Baldessari - Natal Ngétal - Nicolas Hicher - Nir Magnezi - Otherwiseguy - Gabriele Cerami - Pete Zaitcev - Quique Llorente - Radomiropieralski - Rafael Folco - Rlandy - Sagi Shnaidman - shrjoshi - Sławek Kapłoński - Sofer Athlan-Guyot - Soniya Vyas - Sorin Sbarnea - Stephen Finucane - Steve Baker - Steve Linabery - Tobias Urdin - Tony Breeds - Tristan de Cacqueray - Victoria Martinez de la Cruz - Wes Hayutin - Yatin Karel - Zoltan Caplovic *The Next Release Cycle* At the end of one release, focus shifts immediately to the next, Ussuri, which has an estimated GA the week of 11-15 May 2020. The full schedule is available at https://releases.openstack.org/ussuri/schedule.html. Twice during each release cycle, RDO hosts official Test Days <http://rdoproject.org/testday/> shortly after the first and third milestones; therefore, the upcoming test days are 19-20 December 2019 for Milestone One and 16-17 April 2020 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 <http://rdoproject.org/install/packstack/> installation. 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 <http://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 for RDO-specific users and operrators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org <http://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 devel mailing list <https://lists.centos.org/mailman/listinfo/centos-devel> 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 <http://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 and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity <https://twitter.com/rdocommunity>. You can also find us on Facebook <https://www.facebook.com/rdocommunity/> and YouTube <https://www.youtube.com/RDOcommunity>. -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

1 0

[CloudSIG] CentOS Cloud SIG Weekly Mtg Minutes
by Rain Leander 31 Oct '19

31 Oct '19

Meeting started by leanderthal at 15:01:19 UTC (full logs <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…> ). Meeting summary 1. *rollcall* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:02:26) 2. *[leanderthal] TripleO + Kolla packages are available, but...* ( leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:05:31) 1. While the trailing cycle projects are available via the centos mirrors, the altarch packages are not, but we must send the official post no later than today (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:05:41) 2. https://etherpad.openstack.org/p/rdo-train-release-announcement ( leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:05:52) 3. *ACTION*: leanderthal to publish blog post / email lists / schedule social media posts (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:17:48) 3. *[leanderthal] Single Point of Failure wrt: https://bugs.centos.org/view.php?id=16590 <https://bugs.centos.org/view.php?id=16590>* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:18:09) 1. *ACTION*: leanderthal to follow up with rbowen re: redundancy ( leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:39:39) 4. *chair for next week:* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:39:39) 5. *[all] open floor* (leanderthal <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…>, 15:42:11) Meeting ended at 15:46:03 UTC (full logs <https://www.centos.org/minutes/2019/October/centos-meeting.2019-10-31-15.01…> ). Action items 1. leanderthal to publish blog post / email lists / schedule social media posts 2. leanderthal to follow up with rbowen re: redundancy Action items, by person 1. leanderthal 1. leanderthal to publish blog post / email lists / schedule social media posts 2. leanderthal to follow up with rbowen re: redundancy 2. rbowen 1. leanderthal to follow up with rbowen re: redundancy People present (lines said) 1. leanderthal (69) 2. amoralej (63) 3. rbowen (20) 4. centbot (6) 5. mjturek (4) 6. jbrooks (4) -- K Rain Leander OpenStack Community Liaison Open Source Program Office https://www.rdoproject.org/ http://community.redhat.com

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel