devel

devel@lists.centos.org

3 participants
4591 discussions

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

Container rebuilds for Centos-Dockerfiles
by Bamacharan Kundu 21 Mar '17

21 Mar '17

Hi All, We are building most of the dockerfiles from centos-dockerfiles[1] in CentOS Community Container Pipeline[2]. These are built and pushed to registry.centos.org[3]. If there is any update to the source git repo of dockerfile, container gets updated with rebuilt and pushed to registry. Now we are having all the dockerfiles for centos-dockerfiles under same repo[1]. So if there is any change to any of these dockerfiles, all the images gets rebuilt. Which is not required and making the pipeline to get busy for a while. To solve this can we take following routes. 1. Make a single dockerfile to stay in one repo. 2. Make jenkins able to track the exact dockerfile changed. This is not efficient as we need to make sure image is rebuilt when there is change in source codes other than the dockerfile. Could you please share your thoughts on this? Regards Bama Charan Kundu [1] https://github.com/CentOS/CentOS-Dockerfiles [2] https://github.com/CentOS/container-pipeline-service [3] https://wiki.centos.org/ContainerPipeline#head-e288f824ff379a2a14b5ce09c32b…

1 0

Docker centos base image
by Marek Skalický 21 Mar '17

21 Mar '17

Hi, what is a status of CentOS Docker container base image? >From Docker Hub [1] I can see that it was not updated for 3 months. Since this there were two rebuilds of RHEL base image (latest released on 2017-03-02). What is a status of this? Thanks, Marek [1] https://hub.docker.com/_/centos/

5 4

OpenShift in CI
by Marek Skalický 20 Mar '17

20 Mar '17

Hi, what are advantages of having OpenShift in CentOS CI as a service over using `oc cluster up` [1] and deploying it yourself ? Regards, Marek [1] https://github.com/openshift/origin/blob/master/docs/cluster_up_dow n.md

2 1

[SCLo SIG] new sclo-php*-php-* packages available
by Remi Collet 20 Mar '17

20 Mar '17

Just pushed to centos-sclo-sclo stable repository: For rh-php56 * sclo-php56-php-imap-5.6.25-2.el7 (EL-7 only) * sclo-php56-php-smbclient-0.9.0-1 * sclo-php56-php-mcrypt-5.6.28-1 * sclo-php56-php-tidy-5.6.25-1 (EL-7 only) For rh-php70 * sclo-php70-php-imap-7.0.14-2.el7 (EL-7 only) * sclo-php70-php-smbclient-0.9.0-1 * sclo-php70-php-mcrypt-7.0.16-1 * sclo-php70-php-tidy-7.0.10-1 (EL-7 only) Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

[ppc64le] diffs between x86_64 and ppc64le repos: qemu-kvm-ev, cockpit
by Sandro Bonazzola 17 Mar '17

17 Mar '17

Hi, I'm facing some discrepancies in repositories structure for ppc64le. In x86_64 qemu-kvm-ev is shipped within http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/ which is the path I was expecting. Now, looking at ppc64le I see it shipped within: http://mirror.centos.org/altarch/7/extras/ppc64le/Packages/ and being extras enabled by default it overrides qemu-kvm shipped by core os. Can we at least replicate the same structure between http://mirror.centos.org/centos/7 and http://mirror.centos.org/altarch/7 ? next, I see cockpit available for x86_64 in http://mirror.centos.org/centos/7/extras/x86_64/Packages/ but it's missing in http://mirror.centos.org/altarch/7/extras/ppc64le/Packages/ I see cockpit in fedora ppc64le: https://koji.fedoraproject.org/koji/buildinfo?buildID=869569 so it should be possible to get it on centos as well. Can you please build it? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

CentOS PaaS SIG meeting (2017-03-15) Old Time / New Time
by Troy Dawson 15 Mar '17

15 Mar '17

Hello, It's time for our weekly PaaS SIG sync-up meeting In America we just had Daylight Savings Time, so this meeting is really an hour later for those in America. I'm not positive about other countries. To find out the time for you, do the following date -d "1700 UTC" Time: 1700 UTC - Wedensdays Date: Today Wedensday, 15 March 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current StatusI -- rpms -- Documentation -- Automated testing and Automated rpm building -- images / image building -- separate repo work -- minishift - Open Floor

1 1

Re: [CentOS-devel] Service Restored: CentOS Community Container Pipeline
by Bamacharan Kundu 15 Mar '17

15 Mar '17

Hi All, Pipeline is back online and ready accept builds. Regards Bama Charan Kundu On 03/13/2017 02:48 PM, Bamacharan Kundu wrote: > Hi All, > Due to hardware migration work, there would be disruption in CentOS > Community Pipeline Service starting March 13 2017, 23:30 UTC. Though > registry.centos.org will be working and users will be able to pull > images from there. > > Service disruption: CentOS Community Container Pipeline > Start Time : 23:30 UTC, March 13 2017 > End Time : To be notified > Affect : PRs in container-index[1] will not be processed, > update in source repo will not be tracked to > result in updated images in registry.centos.org. > Contact : container-group(a)centos.org > > We will be updating once the service is back online. > Thank you for understanding. > > Note: registry.centos.org will be working as it is. > > Regards > Bama Charan Kundu > > > [1] https://github.com/centos/container-index.git >

1 0

[scl.org] [SCLo SIG] new sclo-php*-php-tidy packages available for testing
by Remi Collet 09 Mar '17

09 Mar '17

Yet another package available in centos-sclo-sclo-testing The php-tidy package contains a dynamic shared object that will add support for using the tidy library to PHP. http://php.net/tidy For rh-php56 (EL-7 only) * sclo-php56-php-tidy-5.6.25-1.el7 For rh-php70 (EL-7 only) * sclo-php70-php-tidy-7.0.10-1.el7 Notices: - this extension is already available in upstream collection for CentOS/RHEL 6 (rh-php56-php-tidy and rh-php70-php-tidy) - this extension requires "libtidy" which is not part of CentOS/RHEL 7, but available in EPEL-7. - in both versions the yum install "rh-phpxx-php-tidy" will work. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

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