devel

devel@lists.centos.org

4 participants
4696 discussions

updated external-repos for CBS with CentOS 6.9
by Fabian Arrotin 05 Apr '17

05 Apr '17

As we announced/released 6.9 today (https://lists.centos.org/pipermail/centos-announce/2017-April/022351.html) , we reflected that in the internal mirror used by koji/cbs.centos.org so from now on, all built content will be built against 6.9. We regenerated also all the metadata from within koji to reflect this. Should you have issues, feel free to discuss those on this list, or #centos-devel on irc.freenode.net -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

CentOS PaaS SIG meeting (2017-03-29)
by Troy Dawson 31 Mar '17

31 Mar '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 March 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- Automated testing and Automated rpm building -- Multi-arch -- separate repo work -- minishift - Open Floor

2 2

Status update on CentOS Community Container Pipeline
by Bamacharan Kundu 30 Mar '17

30 Mar '17

Hi All, Below is updates for the recent works done on CentOS Community Container Pipeline * Clear up the pods and environment once build is complete * Getting all mails from container-pipeline logged in a mailing list * RPM tracking and updating container images based on RPM updates. * Postgresql (upstream) and making sure they work with openshift * Wildfly swarm stack is containerized now. * Ported Alpine based NSQ (https://nsq.io) container image to CentOS * Linter upgrade to prevent the message raised by `FROM` statement Our Current focus is on: * Single mail notification for end to end status for builds in pipeline to user * Setting up external registry * Fixing up current build repeat issue * Refactoring workers to make them more efficient * Fix jenkins issue on CI and debug failing builds on CI * Resolve container dependencies during build * Work on provision to update container images (using jenkins to use a trigger based system to pull in image when new image is pushed to the registry.) * Containerize Kyto Tycoon with the ability to run the same on openshift * Implement the usage of container graph for rpm based rebuilds in controlled and efficient manner. * Integrated container capabilities scanner with scan worker Regards Bama Charan Kundu

1 0

Pull request/Changes to CentOS Extras repo??
by Martin Juhl 28 Mar '17

28 Mar '17

Hi guys... I have some packages in the Extras repo, that I would like to be built for python3 as well as python2... I can provide the changes for the spec files, but what is the official way to commit changes / pull requests???? I would of cource then become the package manager of these packages... (we need them in the COPR project) Regards Martin Juhl

2 1

Providing checksums for our Vagrant images
by Laurentiu Pancescu 23 Mar '17

23 Mar '17

Hi there, I've been looking at making it easier for Vagrant users to verify our images when adding them. The Vagrant documentation mentions that the checksum can be added to the box metadata[1], and that this is done automatically if you build the box on Atlas - indeed, the source code shows they are verifying a checksum from the downloaded metadata[2]. Unfortunately, Atlas does not seem to provide such a checksum for any of the boxes I checked - neither those hosted by them, like debian/jessie64, nor external ones like ours' or Fedora's. The Bento boxes seemed to offer a checksum, but that's just their complete JSON metadata somehow ending up in the description field on Atlas (I assume that's an automatic step not doing what the Bento developers intended - I saw no message about verifying the checksum when adding bento/debian-8.7). We already host the images on cloud.centos.org. We could also generate the needed JSON metadata (we only need one file for all centos/7 images, and one for centos/6), including the SHA256 checksums. We could also create two Apache aliases (e.g. cloud.centos.org/vagrant/7) to make life easier for our users - after an initial "vagrant box add https://cloud.centos.org/vagrant/7", which would prove the checksum automatically, they would also be notified when new images appear and be able to use "vagrant box update centos/7", just like they do now. This would allow us to even move away from Atlas, if desired. We would finally be able to completely automate our Vagrant releases, instead of manually adding the releases to Atlas every month, and not even having embedded checksums. There was an Atlas CLI that proved not to work as expected: our 1701 and 1702 releases didn't end up on Atlas, we had to intervene. The big question is how we could communicate this to our users, not the technical side: I already tested this with a local webserver, serving the centos/7 JSON downloaded from Atlas, which I edited to add an SHA256 checksum - Vagrant automatically verified the checksum after the download was finished. Any thoughts? Laurențiu [1] https://www.vagrantup.com/docs/boxes/format.html#box-metadata [2] https://github.com/mitchellh/vagrant/blob/master/lib/vagrant/action/builtin…

3 6

CentOS PaaS SIG meeting (2017-03-22)
by Troy Dawson 22 Mar '17

22 Mar '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 March 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- images / image building -- Multi-arch -- separate repo work -- minishift - Open Floor

1 1

Status update on CentOS Community Container Pipeline
by Bamacharan Kundu 22 Mar '17

22 Mar '17

Hi All, Here is an update for recent works done on centOS Community Container Pipeline. * Caddy server is now available in registry.centos.org * Nginx with more headers is now available in registry.centos.org * Workers are running from same image now. * Now we support gitlab repos with url ending with .git * Fixed node permissions from provisioning scripts for local 4 machine setup * We are now writing failed build logs to NFS and putting the links to them rather than attaching the log file. Our Current focus is: * Getting all mails logged in a mailing list for tracking the emails received by user. * Tracking RPMs and updating container images based on changes in RPM * Containerize Postgresql (upstream) and making sure they work with openshift * Single mail notification for end to end status with build logs * Integrating container capabilities scanner with scan worker Regards Bama charan Kundu

1 0

CentOS 7.3 docker image for ppc64le is now available
by Murilo Opsfelder Araújo 22 Mar '17

22 Mar '17

Hello, CentOS community. I would like to let you know that a CentOS 7.3 docker image for ppc64le is now available at Docker Hub: https://hub.docker.com/r/ppc64le/centos/ We proceed investigating CentOS Container Pipeline to include it in CentOS Registry. -- Murilo

5 9

Announcing BugFix Release of Linch-Pin v0.9.1
by Clint Savage 21 Mar '17

21 Mar '17

Released today is the v0.9.1 update to the hybrid cloud provisioner, Linch-Pin. In the release are the following updates / bugfixes: * Updated linchpin_config variable to fix config file resolution * Set default res_grp_vars when res_grp_vars in not defined for aws_ec2 * linchpin config --reset now generates correct schema The release is available via pypi at this time. The web url for the package is https://pypi.python.org/pypi?name=linchpin&version=0.9.1&:action=display Feel free to download from here, or perform a pip install linchpin==0.9.1 Release information provided above was copied from the official release on github and can be viewed at https://github.com/CentOS-PaaS-SIG/linch-pin/releases/tag/v0.9.1 Future bugfix releases will be made as needed, based upon issues presented on our github issue tracker at https://github.com/CentOS-PaaS-SIG/linch-pin/issues Thanks to everyone for the hard work on this project. Let's keep making Linch-Pin great! Cheers, herlo

1 0

Minishift in PaaS SIG
by Lalatendu Mohanty 21 Mar '17

21 Mar '17

Hi All, In last couple of Paas SIG meetings we discussed around if we should provide Minishift from PaaS SIG and the general agreement was that it will benefit the CentOS community. As a member of Minishift project and PaaS SIG member I will work to build Minishift in the CentOS build system and doing the releases through PaaS SIG. I have copied the recent release announcement of Minishift in this mail to give you some context about Minishift . Previously we were working on Atomic Developer Bundle (ADB) which was part of Atomic SIG. Minishift is the next generation tool to replace ADB as it address lot of ADB's short comings. It is written in Go and it is light weight and designed to provide better user experience. We have been doing couple of beta releases in Minishift project as we move towards the 1.0.0 release. The next release is planned to be a release candidate release then followed by 1.0.0 release. If you are interested to help us in building, testing, releasing Minishift through PaaS SIG, please let us know. *Release announcement for Minishift 1.0.0-Beta.5 : * The Minishift team is pleased to announce the release of Minishift 1.0.0 Beta 5. Minishift [1] is a command-line tool that provisions and manages single-node OpenShift clusters optimized for development workflows. You can run Minishift on GNU/Linux, Microsoft Windows or macOS. Release highlights ------------------------ This release adds several features, enhancements, and bug fixes, including: - Minishift is now configured to use nip.io instead of xip.io [4]. - The default routes for application will be created with the <VM IP>. nip.io routing suffix. - The sudoers role was added to the “developer” user [5]. - This role allows the “developer” to impersonate system:admin when running a command. For example, you can run “$ oc get nodes --as system:admin” while logged in as the developer user. - An important bug for proxy server (http/https) support was fixed [10]. - We had a bug where registration was failing in proxy environments. - OpenShift related subcommands from the root context were moved under the “minishift openshift” command [11]. This release also includes many changes and bug fixes, which are detailed in the release notes [2] and milestone [3] . For information about getting started, using, and developing Minishift, see the documentation [6]. Additional components ----------------------------- - We released new versions of the Boot2Docker ISO (v1.0.2) [ 8] and the CentOS ISO (v1.0.0-rc3) [7] images. - We added the ‘fuse-sshfs’ package to both the ISO images. With SSHFS, users can mount host folders. Currently this is a manual process [9] but we are working on automating it. Please give the new release a try and let us know your feedback. The Minishift community hangs out at #minishift channel on Freenode and it is the perfect place to discuss anything Minishift related. [1] https://github.com/minishift/minishift [2] https://github.com/minishift/minishift/releases/tag/v1.0.0-beta.5 [3] https://github.com/minishift/minishift/milestone/10 [4] https://github.com/minishift/minishift/issues/501 [5] https://github.com/minishift/minishift/issues/509 [6] https://github.com/minishift/minishift#documentation [7] https://github.com/minishift/minishift-centos-iso/releases/tag/v1.0.0-rc.3 [8] https://github.com/minishift/minishift-b2d-iso/releases/tag/v1.0.2 [9] https://github.com/minishift/minishift/blob/master/docs/managing-minishift.… [10] https://github.com/minishift/minishift/issues/489 [11] https://github.com/minishift/minishift/issues/465 Thanks, Lala

2 7

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel