devel

devel@lists.centos.org

10 participants
4617 discussions

Bug #12169 not yet fixed
by Laurentiu Pancescu 26 Jul '17

26 Jul '17

Hello Fabian and Thomas, I think bug #12169 might have been closed prematurely (again). The reported issue is that %addon sections are ignored by CBS, not that we need to upgrade our infra to CentOS Linux 7 (that was just what we initially thought to be enough to avoid the problem). The problem was that pykickstart had no support for %addon sections, and it removed any unknown section from generated file. I reported this upstream a while ago, and Chris Lumens added a workaround 12 days ago. [2] Could we incorporate the two upstream commits into our .srpm and let me test it first, please? :) Thanks, Laurențiu [1] https://bugs.centos.org/view.php?id=12169 [2] https://github.com/rhinstaller/pykickstart/issues/154#issuecomment-314172112

2 2

MATROX GPU - xorg-x11-drv-mga-1.6.3 on supermicro server
by Andreas Benzler 23 Jul '17

23 Jul '17

Hello Guys, our cluster runs till 2014 on supermicro board. It is not unusual that still mainboards with mga graphics cards are delivered. So I have then adjusted the mga driver from centos 6 - the specification file - , to be build on CentOS 7. Since then this runs on the headnode without failures. Maybe you should provide this via epel. The source can be found here: http://centos.cms4all.org/repo/7/drivers/SRPM/xorg-x11-drv-mga-1.6.3-11.el7… This is the latest from Centos 6.9. Sincerely Andy

2 2

LinchPin v1.0.2 (bugfix) has been released
by Clint Savage 20 Jul '17

20 Jul '17

Hi all, We are happy to announce that LinchPin v1.0.1 has been released. This is a bugfix release, which fixed the following issues: #279 - Make a default path for credentials #288 - Updates to beaker provisioner #290 - Recommended fixes from landscape.io #298 - Remove .yaml from output resources files #308 - installing deps requires -y flag One enhancement was included: #281 - More documentation updates The official release notes are available at https://github.com/CentOS-P aaS-SIG/linchpin/blob/develop/docs/source/release/RELEASE_1_0_2.rst This update is available via PyPi. Packages will be available as soon as possible. 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

1 0

CentOS PaaS SIG meeting (2017-07-19)
by Troy Dawson 19 Jul '17

19 Jul '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 19 July 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- minishift -- kompose -- Images and Image building - Open Floor

1 1

Update on CentOS Community Container Pipeline
by Bamacharan Kundu 19 Jul '17

19 Jul '17

Hi All, Here is recent updates on CentOS Community Container Pipeline. * Issues with jenkins for proceeding with builds even in failure are fixed now. * Issues with workers not deleting jobs properly in case of failure are fixed now. * Jenkins is updated with security fixes * Repeating failed builds are checked and fixed now * Updated service logs for better visibility and proper level * Openshift projects are now cleaned up properly before running a build. * UI for registry is set up on pre-prod * Jenkins jobs are now synced up regularly with container-index. On update or removal of existing entries in container-index, Jobs gets updated or deleted. Our current focus is on: * Builds to be serialized after the linter is successful * Setting up monitoring tool for getting application errors fix them quickly, * Fixing index reader to read proper value in string format (currently it reads numeric values a number and truncates it) * Adding functional and test cases for more coverage around failed cases * Provisioning for cleaning up the current environment before a deployment of the service. Regards Bamacharan Kundu

1 0

CentOS Atomic Host 7.1706 Released
by Jason Brooks 18 Jul '17

18 Jul '17

An updated version of CentOS Atomic Host (tree version 7.1706), is now available. [1] CentOS Atomic Host is a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org. CentOS Atomic Host includes these core component versions: - atomic-1.17.2-9.git2760e30.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.6-32.git88a4867.el7.centos.x86_64 - etcd-3.1.9-1.el7.x86_64 - flannel-0.7.1-1.el7.x86_64 - kernel-3.10.0-514.26.2.el7.x86_64 - kubernetes-node-1.5.2-0.7.git269f928.el7.x86_64 - ostree-2017.5-3.el7.x86_64 - rpm-ostree-client-2017.5-1.atomic.el7.x86_64 Containerized kubernetes-master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. Instead, you can run the master kubernetes components (apiserver, scheduler, and controller-manager) in containers, managed via systemd, using the service files and instructions on the CentOS wiki. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline, based on Dockerfiles from the CentOS-Dockerfiles repository. These containers have been tested with the kubernetes ansible scripts provided in the upstream contrib repository, and they work as expected, provided you first copy the service files onto your master. Alternatively, you can install the kubernetes-master components using rpm-ostree package layering using the command: atomic host install kubernetes-master. Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade Images Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box are Vagrant boxes for Libvirt and Virtualbox providers. The easiest way to consume these images is via the Atlas / Vagrant Cloud setup (see https://atlas.hashicorp.com/centos/boxes/atomic-host) For example, getting the VirtualBox instance up would involve running the following two commands on a machine with vagrant installed: $ vagrant init centos/atomic-host && vagrant up --provider virtualbox ISO The installer ISO can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This image allows users to control the install using kickstarts and to define custom storage, networking and user accounts. This is the recommended option for getting CentOS Atomic Host onto bare metal machines, or for generating your own image sets for custom environments. QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2 image is suitable for use in on-premise and local virtualized environments. We test this on OpenStack, AWS and local Libvirt installs. If your virtualization platform does not provide its own cloud-init metadata source, you can create your own NoCloud iso image. Amazon Machine Images Region Image ID ---------------- -------------- us-east-1 ami-70e8fd66 ap-south-1 ami-c0c4bdaf eu-west-2 ami-dba8bebf eu-west-1 ami-42b6593b ap-northeast-2 ami-7b5e8015 ap-northeast-1 ami-597a9e3f sa-east-1 ami-95aedaf9 ca-central-1 ami-473e8123 ap-southeast-1 ami-93b425f0 ap-southeast-2 ami-e1332f82 eu-central-1 ami-e95ffd86 us-east-2 ami-1690b173 us-west-1 ami-189fb178 us-west-2 ami-a52a34dc SHA Sums f854d6ea3fd63b887d644b1a5642607450826bbb19a5e5863b673936790fb4a4 CentOS-Atomic-Host-7.1706-GenericCloud.qcow2 9e35d7933f5f36f9615dccdde1469fcbf75d00a77b327bdeee3dbcd9fe2dd7ac CentOS-Atomic-Host-7.1706-GenericCloud.qcow2.gz 836a27ff7f459089796ccd6cf02fcafd0d205935128acbb8f71fb87f4edb6f6e CentOS-Atomic-Host-7.1706-GenericCloud.qcow2.xz e15dded673f21e094ecc13d498bf9d3f8cf8653282cd1c83e5d163ce47bc5c4f CentOS-Atomic-Host-7.1706-Installer.iso 5266a753fa12c957751b5abba68e6145711c73663905cdb30a81cd82bb906457 CentOS-Atomic-Host-7.1706-Vagrant-Libvirt.box b85c51420de9099f8e1e93f033572f28efbd88edd9d0823c1b9bafa4216210fd CentOS-Atomic-Host-7.1706-Vagrant-VirtualBox.box 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, based on upstream work from Project Atomic. If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the 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 mailing list. Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

1 0

Proposed changes to CentOS Atomic SIG meetings
by Jason Brooks 18 Jul '17

18 Jul '17

The members of the CentOS Atomic SIG have discussed adjusting our meeting schedule to accommodate more time zones, and to consolidate our meetings somewhat with the upstream Project Atomic meetings. We propose moving the CentOS Atomic SIG meeting to occur every two weeks, on Mondays, at 0400 UTC, to alternate with the every-two-week atomic sig meeting that occurs on Mondays at 1600 UTC. The idea is that the 0400 UTC meetings will accommodate community members in Bangalore, the 1600 UTC meeting will accommodate Eastern US and European members, and both times are accessible to the US west coast. The next Project Atomic community meeting is scheduled for July 24th and 1600 UTC, and the first CentOS Atomic SIG meeting on the new schedule would be at 0400 UTC on July 31st. The Project Atomic community meeting takes place on freenode in #atomic. We'd like to start holding the CentOS Atomic SIG meeting in #atomic as well, to promote collaboration with other atomic community members. Questions, concerns, etc? Regards, Jason

1 0

Updating golang in CentOS Extras?
by Niels de Vos 17 Jul '17

17 Jul '17

Hi, Currently CentOS Extras contains golang-1.4.2, but newer versions have been released since. Is there a plan for updating golang any time soon? In the CentOS Storage SIG we have a package (heketi) that started to depend on golang-1.6.2 (iirc). For us the older version of Golang in Extrasa results in preventing to update Heketi, and so users will not get the new features that are released upstream. If Extras can not get a newer version of Golang (soonish), what is the preferred approach to make an updated version of Golang available for repositories in a SIG? Thanks! Niels

3 4

Introduction to Cloud Programming with GreatFree
by Bing Li 17 Jul '17

17 Jul '17

*GreatFree? Cloud Programming? Why?* *Bing Li* *bing.li(a)asu.edu <bing.li(a)asu.edu>* GreatFree is a cloud programming environment I invented during the past seven years gradually. Using it, developers are able to program any distributed systems in any distributed computing environments rapidly and flexibly. To the best of my knowledge, this ought to be the first tool that attains this goal at this moment. You must not believe? If not, could you please tell me any other ones else? First of all, I need to define the term of programming from my prospective. Programming is the technology that offers developers the way to implement a software system with their knowledge in the specific domain only. According to that, when developers implement a distributed system, especially over the Internet, there is no such a tool, a programming environment or a programming language. Thus, two choices are always employed by them. The first one is to construct their systems over existing frameworks. Each of those frameworks focuses on one specific system only. Most domain-specific issues have already been resolved within the frameworks such that developers do not need to take into account them. Rather, developers work with script languages that are completely independent of the specific distributed environment. In contrast, another choice is to implement the system with a generic programming language. Unfortunately, this is a nightmare since they have to take care of not only domain knowledge of their systems but also thousands of details that have nothing to do with the specific domain. Although developers can implement distributed systems through the two alternative ways, simple or difficult, that is not programming from my perspective. Why is it so important to apply developers’ domain knowledge when implementing a software system? The answer is the freedom of development. Developers have the highest flexibility when programming distributed systems over the Internet with generic programming languages. However, it is too tough to tolerate such that only super guys might choose this way. We just forget about it. On the other hand, although it is convenient to do that with existing frameworks, developers lose almost all of the freedom to construct the system according to their expectations and knowledge since they are even not aware of any distributed issues. For consumers, that is fine. However, for developers, that is unacceptable. Without learning the internal structures, automobile developers are degenerated to drivers. Without grasping distributed knowledge, software developers can be replaced by high school students. Moreover, I believe programming with developers’ skills and knowledge is an activity full of joy. Proficient guys would like to manipulate a tool that provides them with rich options and choices rather than the fully-automatic one. Finally, from the academic point of view, it is weird that a programming tool is not available for the development of distributed system over the Internet. What scares computer scientists? With respect to the above discussions, I propose the tool, GreatFree, a new cloud programming environment, which allows developers to apply their distributed knowledge and skills as well as abandon any other irrelevant issues. Additionally, with its skillful designs, it also achieves the goal of rapid development. The concept of programming is realized in practice in the domain of the Internet distributed systems development. Now its initial version is available online. It is making progresses to push it to be the generic language for any distributed systems development. You are welcome to taste it. I appreciate so much for any suggestions! Finally, I need to indicate the relation between GreatFree and cloud programming. As one important instance of distributed systems over the Internet, no programming tools are available for cloud systems as well. Since it is so popular, I would like to entitle GreatFree together with the technology of cloud programming although GreatFree can also be used to program non-cloud systems. Incidentally, if you search the keyword, cloud programming, over the Web, you can get some results. Unfortunately, GreatFree is different from them in nature. Those stuffs look more like new generic languages with limited distributed features rather than the one to program the Internet-based distributed systems. You can get the presentation slides from the below link: *http://greatfree.lofter.com/post/1d231e0d_1069dcc5 <http://greatfree.lofter.com/post/1d231e0d_1069dcc5>* The APIs of GreatFree is as follows: *http://greatfree.0fees.us <http://greatfree.0fees.us>* The book and source code are downloadable at the link: *https://github.com/greatfree/Programming-Clouds <https://github.com/greatfree/Programming-Clouds>* Thanks so much! Best regards, Bing Li

1 0

CentOS PaaS SIG meeting (2017-12-05)
by Troy Dawson 12 Jul '17

12 Jul '17

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

1 1

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