devel

devel@lists.centos.org

10 participants
4617 discussions

CentOS PaaS SIG meeting (2017-12-06)
by Troy Dawson 06 Dec '17

06 Dec '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 06 December 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building -- minishift / kompose / kedge - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2017/November/centos-devel.2017-11-28-15.05.…

1 0

New Version of CentOS Atomic Host Available for Download
by Jason Brooks 05 Dec '17

05 Dec '17

Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1711), a lean operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. This release rolls up a handful of minor CentOS updates from the past month. The core Atomic component versions are unchanged from those in the previous release (7.1710). CentOS Atomic Host includes these core component versions: * atomic-1.19.1-5.git48c224b.el7.centos.x86_64 * cloud-init-0.7.9-9.el7.centos.2.x86_64 * docker-1.12.6-61.git85d7426.el7.centos.x86_64 * etcd-3.2.7-1.el7.x86_64 * flannel-0.7.1-2.el7.x86_64 * kernel-3.10.0-693.5.2.el7.x86_64 * kubernetes-node-1.5.2-0.7.git269f928.el7.x86_64 * ostree-2017.11-1.el7.x86_64 * rpm-ostree-client-2017.9-1.atomic.el7.x86_64 # Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) # Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade # Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. # Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream work from Project Atomic (http://www.projectatomic.io/) If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets every two weeks as part of the Project Atomic community meeting at 16:00 UTC on Monday in the #atomic channel. You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. # Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

[Cloud] OpenStack/RDO test day, Queens Milestone 2, December 14, 15
by Rich Bowen 04 Dec '17

04 Dec '17

Join us next Thursday and Friday as we test Queens Milestone 2 - the next version of OpenStack. http://rdoproject.org/testday/queens/milestone2/ This time, we're doing something a little different. For those of you who don't have the time, patience, or hardware to spin up your own OpenStack cloud, we'll have one ready for you. You can just log in, try it out, try your work loads, try to break things. We're hoping, with this change, to open test day to a wider audience of users and operators. If you're interested in participating in this test, and seeing what's coming in February, read this blog post [1] and sign up here [2] for your login credentials. Please also consider amplifying this invitation by following @RDOCommunity on Twitter, and retweeting the invitations to test day, as well as by sending this message to other relevant mailing lists. Thanks! [1] https://dmsimard.com/2017/11/29/come-try-a-real-openstack-queens-deployment/ [2] https://etherpad.openstack.org/p/rdo-queens-m2-cloud -- Rich Bowen - rbowen(a)redhat.com http://rdoproject.org @RDOCommunity

1 0

where should we build nsible-2.4.1 in CBS?
by Ken Dreyer 01 Dec '17

01 Dec '17

Hi folks, The latest ceph-ansible version requires ansible-2.4.1.0 now, due to some regressions in ansible-2.4.0.0. It looks like the "ansible" package in CBS has been built in several different build targets recently. Is there a standard place where we can build the "ansible" package going forward, and then cross-tag that build into all the places that need it? - Ken

4 9

CentOS PaaS SIG meeting (2017-11-29)
by Troy Dawson 29 Nov '17

29 Nov '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 29 November 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building -- minishift / kompose / kedge - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2017/November/centos-devel.2017-11-22-17.01.…

1 0

Fwd: Removing mongodb from RDO
by Alfredo Moralejo Alonso 24 Nov '17

24 Nov '17

Note that mongodb will not longer be maintained in RDO. I've observed it's cross-tagged in infrastructure7-testing so it may impact someone out of CloudSIG. Best regards, Alfredo ---------- Forwarded message ---------- From: Alfredo Moralejo Alonso <amoralej(a)redhat.com> Date: Fri, Nov 24, 2017 at 4:00 PM Subject: Removing mongodb from RDO To: dev(a)lists.rdoproject.org, users(a)lists.rdoproject.org Hi, During previous OpenStack releases, projects using mongodb as backend (as telemetry or zaqar) have moved to other technologies for data persistence and mongo is not longer the default or preferred backend. In this cycle (Queens), mongodb packages will be retired from RDO repositories under the assumption that users have implemented any of the alternatives for each affected service (or are in the process of doing it). This will happen in next weeks and will not affect previous releases. If you have any question or you think that mongo should be maintained in RDO, please feel free to let us know in this thread or reach us in #rdo so that we can consider all implications of this decision. Best regards, Alfredo

2 1

[Cloud SIG] Fwd: [openstack-dev] FOSDEM 2018: Call For Proposals: Virtualization & IaaS DevRoom
by Rich Bowen 22 Nov '17

22 Nov '17

For those who may not have seen this yet: The deadline for the call for papers for the IaaS devroom at FOSDEM is a little more than a week away. Full details are provided below. FOSDEM is a great opportunity to get the word out to an enthusiastic, mostly young audience. And it's a fun event. You should come. -------- Forwarded Message -------- Subject: [openstack-dev] FOSDEM 2018: Call For Proposals: Virtualization & IaaS DevRoom Date: Mon, 6 Nov 2017 13:37:10 +0100 From: Kashyap Chamarthy <kchamart(a)redhat.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: openstack-dev(a)lists.openstack.org I'm delighted to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2018, to be hosted on February 3 and 4, 2018. This year will mark FOSDEM’s 18th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. FOSDEM will be held once again in Brussels, Belgium, on February 3 & 4, 2018. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, libvirt, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 1st, 2017. --------------- Important Dates --------------- Submission deadline: 01 December 2017 Acceptance notifications: 14 December 2017 Final schedule announcement: 21 December 2017 Devroom: 03 and 04 February 2018 (two days- different rooms) ----------------- About the Devroom ----------------- The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as Apache CloudStack, OpenStack, oVirt, QEMU, OpenNebula, and Ganeti. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. -------------------- Submit Your Proposal -------------------- All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. --------------------- Submission Guidelines --------------------- We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 45 minutes, with 35 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) ------------------------- Speaker Mentoring Program ------------------------- As a part of the rising efforts to grow our communities and encourage a diverse and inclusive conference ecosystem, we're happy to announce that we'll be offering mentoring for new speakers. Our mentors can help you with tasks such as reviewing your abstract, reviewing your presentation outline or slides, or practicing your talk with you. You may apply to the mentoring program as a newcomer speaker if you: Never presented before or Presented only lightning talks or Presented full-length talks at small meetups (<50 ppl) --------------------- Submission Guidelines --------------------- Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. ------------ How to Apply ------------ In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. ---------------- Call for Mentors ---------------- Interested in mentoring newcomer speakers? We'd love to have your help! Please email iaas-virt-devroom at lists.fosdem.org with a short speaker biography and any specific fields of expertise (for example, KVM, OpenStack, storage, etc.) so that we can match you with a newcomer speaker from a similar field. Estimated time investment can be as low as a 5-10 hours in total, usually distributed weekly or bi-weekly. Never mentored a newcomer speaker but interested to try? As the mentoring program coordinator, email Brian Proffitt[3] and he will be happy to answer your questions! --------------- Code of Conduct --------------- Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. ------------------- Call for Volunteers ------------------- We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact me, Brian Proffitt, for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM18> https://penta.fosdem.org/submission/FOSDEM18 [2] iaas-virt-devroom at lists.fosdem.org <https://lists.fosdem.org/listinfo/fosdem> [3] bkp at redhat.com -- /kashyap __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

CentOS PaaS SIG meeting (2017-11-22)
by Troy Dawson 22 Nov '17

22 Nov '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 22 November 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building -- minishift / kompose / kedge - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2017/November/centos-devel.2017-11-15-17.00.…

1 0

LinchPin v1.2.0 has been released
by Clint Savage 21 Nov '17

21 Nov '17

Hi all, We are happy to announce that LinchPin v1.2.0 has been released. This is an enhancement release, which has the following updates: runDB - Provides a centralized json (tinydb) database for tracking provisioning transactions - A run_id is now assigned to each transaction - A 'unique-ish' hash is assigned to each transaction, some providers use this in the naming of the instances - The the most recent 'up' transaction in the database is used on any destroy actions - A --run-id (-r) flag can be passed to idempotently provision, or destroy any specific transaction Deprecate output_writer role. Use gather_resources role, which refers to runDB as appropriate. The libvirt module has multiple improvements - Enhanced schema to enable cloud_config for cloud-init functionality - Libvirt functionality can now be run on a remote system - SSH keys can be passed using the cloud-init ssh-import-id functionality - Keys can be copied from the local system or from remote locations - This supports downloading keys from github and launchpad - Enabled virt console for troubleshooting issues - May require privilege escalation to copy images and keys Linchpin Journal - provides output from the runDB for each transaction Openstack can now boot from an image Docker images now perform integration testing Installation documentation improvements The official release notes are available at https://github.com/CentOS-PaaS -SIG/linchpin/releases/tag/v1.2.0 This update is available via PyPI: https://pypi.python.org/pypi/linchpin If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues) Cheers and enjoy! Clint Savage LinchPin Maintainer Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin

1 0

PaaS-sig help
by Brigman, Larry 16 Nov '17

16 Nov '17

I'm interesting in supporting PaaS-sig in areas of testing and documentation writing. Let me know how I can help.

3 2

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