February 2018 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

SRPMS for AltArch (more specifically aarch64 kernel)
by Dominique Martinet 22 Aug '18

22 Aug '18

Hi folks, I've asked on IRC and have been pointed to this list. I can't seem to find this particular source rpm: kernel-aarch64-4.5.0-29.el7.src.rpm which is what is pointed by `rpm -qi kernel` on my system. Are these supposed to be available anywhere? Looking on google I only see one for an older release in someone's centos user/people page, but I can't seem to find these in any repo. The debuginfo are properly here but it's good to have sources as well when messing around with low level stuff :) Cheers and thanks for the hard work, -- Dominique Martinet

3 8

Notes from CERN pre-dojo
by Rich Bowen 23 May '18

23 May '18

The notes from the pre-dojo meeting at CERN, yesterday, may be found in the etherpad at https://public.etherpad-mozilla.org/p/cern-centos-thursday Those involved in the various discussion topics are requested to elaborate, where appropriate. Thanks to everyone who attended this very productive discussion. --Rich -- -- Rich Bowen - rbowen(a)redhat.com @rbowen // @rdocommunity // @CentOSProject 859 351 9166

5 7

LinchPin v1.5.1 (update) has been released
by Clint Savage 09 Apr '18

09 Apr '18

We are happy to announce that LinchPin v1.5.1 has been released. This release has the following updates: * The command line shell now enables ansible verbose output (#456) * Made the uHash optional for instances and inventory files (#458) * Adjusted the default location of the RunDB to the workspace (#458) * General cleanup (#461) * Update the README * Remove references to outdated documentation. * Remove unused schemas and documentation. * Fixed documentation example links (#453) * Make generating resources optional (#462) * Additional libvirt updates (#464) * Add detail about libvirt and image copying rights to Provider doc * Libvirt supports 'become' functionality as an unprivileged user * Additional Documentation improvements to Getting Started Guide (#464) * Updated `mkvirtualenv` docs to point out the ``-p`` switch for newer distros with Python 3.x installed * Made aws topology option `keypair` optional (#466) The official release notes are available at https://github.com/CentOS-PaaS-SIG/linchpin/releases/tag/v1.5.1 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 1

CentOS Storage SIG contribution.
by Javier Romero 02 Mar '18

02 Mar '18

Hi, My name is Javier, live in Buenos Aires, Argentina, and work in the Network Operations Center of an Internet Service Provider as a Linux Sysadmin. I've been working with Linux CentOS Servers for the last 10 years and would like to contribute on the CentOS Storage SIG if there is something where I can be useful. Thanks for your kind attention. Best Regards, *Javier Romero* *E-mail: xavinux(a)gmail.com <xavinux(a)gmail.com>* *Skype: xavinux*

2 13

Bot account for opstools-sig
by Matthias Runge 02 Mar '18

02 Mar '18

Hello, as follow-up on the CentOS dojo in Geneva, I'm hereby requesting a bot account for the Opstools SIG. There are listed two requirements[1]: - the account name is the shortname for the SIG: I'm proposing opstools - The email on the account must be deliverable to someone who can change the certificate on the production environment. The opstools SIG uses RDO gerrit for kicking off builds. So, either we'd need here the email address of someone with such access to RDO gerrit. I currently have no such login. Whatever works here, I'd be fine with it. I did not create an account in ACO yet, since the email question is currently undecided. [1] https://wiki.centos.org/SIGGuide#head-c256691b201cc88e4ffa53f3dee8c78b8cdca… -- Matthias Runge <mrunge(a)matthias-runge.de>

2 2

CentOS PaaS SIG meeting (2018-02-28)
by Troy Dawson 28 Feb '18

28 Feb '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 28 February 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building - Upcomming Committee Member Changes - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-21-17.01.…

1 0

Status Update: CentOS Community Container Pipeline Service 28-Feb-2018
by Bamacharan Kundu 28 Feb '18

28 Feb '18

Hi All, Here is an update on the recent works done in Centos Community Container Pipeline * https://registry.centos.org is updated with new UI allowing users * search through the content * shows the dockerfile from which the image is built * Shows the Readme from the repo which mostly talks about the usage of the image * We have refactored garbage collector to get proper diff in container-index and registry.centos.org for removing extra images pushed to registry in build time. * We have disable the centos/centos:* base images to be excluded in RPM repo tracking. This will make sure these images are only updated in case of changes pushed to source repo. Our recent focus is: * We are developing API for exposing the build data from back end to show more details in registry UI. * Fixing beanstalk connection initialization method * Fix pre-build job entries CI to not check for target file * Fixes bug in dangling volume cleanup post scan * Prevents logging unnecessary recurring queue operational messages Regards Bamacharan Kundu

1 0

Email alias for SIG members?
by Matthias Runge 28 Feb '18

28 Feb '18

Hello, I recently thought about the possibility of getting an email alias for SIG members. That should not be forwarded to a mailing list. Would something like that be possible? Idea is to spam people in charge directly. It can contain sensitive data, or data not belonging to mailing lists, like certificates, build failures, that kind of thing. Other than that, all communication should be kept public, IMHO. So: would it be possible to get an email alias like <sig-name>@centos.org to forward emails? If yes, what would be the process? Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

1 0

Re: [CentOS-devel] CentOS for IBM Mainframes.
by David Edelsohn 27 Feb '18

27 Feb '18

>>>>> Javier Romero writes: > Is there any chance that IBM donate this hardware for the CentOS > project? Think that will be also useful for that company to have > another Linux distro running on their Z Systems. IBM can and does provide raw z/VM VMs at Marist or Syracuse for other Linux distros, such as Debian. That is what you really need, not "hardware". The discussion about donating hardware is off track. The Debian support is completely community driven and maintained. If there is a group of CentOS developers who want to bootstrap and maintain it, the resources probably can be made available. If this is a request for IBM to enable CentOS on IBMz, that is an orthogonal discussion about IBM resources and likely would require IBM customer demand. Thanks, David

4 10

Two New Committee Members Needed for CentOS PAAS SIG
by Troy Dawson 27 Feb '18

27 Feb '18

Hello, Due to "Real Life" the following CentOS PAAS Sig committee members will be leaving the committee, on the following dates. We will need to get replacements for them by those dates. Ari LiVigni - March 14th Troy Dawson - May 15th Ari is in charge of Automation. Troy is the committee chairman. The CentOS PAAS Sig has been very successful in bringing a free version of OpenShift to everyone. These two people have been a very large part of that. They will be missed. But it's time to look to the future. We need people to step up and not only fill their shoes, but continue to move forward. Take a minute and see if this is something that you would want to do. If it is, please let us know.

1 1

New sclo-php##-phpiredis 1.0.0 packages available for testing
by Remi Collet 23 Feb '18

23 Feb '18

New packages available in centos-sclo-sclo-testing Phpiredis is an extension for PHP 5.x and 7.x based on hiredis that provides a simple and efficient client for Redis and a fast incremental parser / serializer for the RESP protocol. For rh-php56 * sclo-php56-php-phpiredis-1.0.0-1 For rh-php70 * sclo-php70-php-phpiredis-1.0.0-1 For rh-php71 * sclo-php71-php-phpiredis-1.0.0-1 This extension is also an accelerator used by the Predis pure-PHP library (https://packagist.org/packages/predis/predis) Sometime ago I wrote a blog entry about Redis access from PHP: https://blog.remirepo.net/post/2016/11/13/Redis-from-PHP Feedback welcome. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Fwd: [Arm-dev] Kubernetes support on ARM32
by Fabian Arrotin 23 Feb '18

23 Feb '18

Forwarding this to centos-devel, as that's where other discussions around kubernetes rebuild[s] takes place too. What would be the best way to to have people from armhfp world discussing with the people managing/maintaing k8s on cbs.centos.org ? Just opening a thread about this, but it's good to know that : - people are willing to (re)build it for armhfp - and that it works with just rebuilding the src.rpm from cbs.centos.org (covering so far x86_64, while aarch64, ppc64le are also other available target arches in koji/cbs) BTW, kudos to Wagner Sartori (trunet) for the rebuild ! :-) -------- Forwarded Message -------- Subject: {Disarmed} [Arm-dev] Kubernetes support on ARM32 Date: Fri, 23 Feb 2018 06:13:48 -0300 (BRT) From: Trunet <trunet-centos(a)wsartori.com> Reply-To: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> To: arm-dev <arm-dev(a)centos.org> Hey, what's up! I finished building all needed packages to bring kubernetes to ARM. All of them were brought by simply copying src packages from CBS and doing minor or no changes at all. To my surprise, kubeadm ran perfectly fine, it got the correspondent arm image for each component. I went with weave for pod network layer, as it have network policy and ARM support. Manual changes, was to symlink all files under /opt/cni/bin into /usr/libexec/cni, otherwise the pods will not find the cni plugins and doesn't start (like kube-dns stuck at containercreating). And kubernetes-dashboard, you need to change tha image to be arm instead of amd64. Repo is here: https://armv7.dev.centos.org/repodir/community-kubernetes-testing/ =================================== # kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"archive", BuildDate:"2018-02-22T14:26:58Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} # kubectl cluster-info Kubernetes master is running at https://192.168.x.x:6443 KubeDNS is running at *MailScanner warning: numerical links are often malicious:* https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn… <https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn…> To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. =================================== Thanks for Arrfab for setting up the build environment and repository. Best regards, Wagner Sartori Junior

1 0

Kubernetes support on ARM32
by Trunet 23 Feb '18

23 Feb '18

Hey, what's up! I finished building all needed packages to bring kubernetes to ARM. All of them were brought by simply copying src packages from CBS and doing minor or no changes at all. To my surprise, kubeadm ran perfectly fine, it got the correspondent arm image for each component. I went with weave for pod network layer, as it have network policy and ARM support. Manual changes, was to symlink all files under /opt/cni/bin into /usr/libexec/cni, otherwise the pods will not find the cni plugins and doesn't start (like kube-dns stuck at containercreating). And kubernetes-dashboard, you need to change tha image to be arm instead of amd64. Repo is here: https://armv7.dev.centos.org/repodir/community-kubernetes-testing/ =================================== # kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"archive", BuildDate:"2018-02-22T14:26:58Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} # kubectl cluster-info Kubernetes master is running at https://192.168.x.x:6443/ KubeDNS is running at https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn… To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. =================================== Thanks for Arrfab for setting up the build environment and repository. Best regards, Wagner Sartori Junior

1 0

[Cloud SIG] meeting minutes, Feb 22, 2018
by Rich Bowen 22 Feb '18

22 Feb '18

Thanks to those that attended today's Cloud SIG meeting. We were particularly pleased to welcome Rohit Yadav, from the Apache CloudStack community, and we look forward to the Cloud SIG no longer being a monoculture. Minutes: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Minutes (text): https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Log: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Next week's meeting will be at the same time - 15:00 UTC, Thursday March 1, on #centos-devel on Freenode (I will be traveling, and thus absent, so if someone else can step up to chair this meeting, that would be greatly appreciated.) -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

1 0

[Cloud SIG] CloudStack publishing effort in CentOS
by Rohit Yadav 22 Feb '18

22 Feb '18

Hi all, (/cc cloudstack-dev) I'm Rohit Yadav, committer/pmc from the Apache CloudStack [1] community. Apache CloudStack is an IaaS cloud computing platform. I've been maintaining and publishing the CloudStack noredist repos [3][4] for few years now, and I would like to get them published to the official CentOS (and other distros) repositories. I met Rich during Fosdem yesterday and he suggested to reach out to the cloud-sig/list [2] to discuss how we can get CloudStack rpms into CentOS. I understand in the past we were not very successful at that, but I want to make a second attempt especially since we've introduced the concept of LTS releases in CloudStack. I'm not sure if the devel list is the right place or if an explicit cloud-sig list exists [2], so please advise -- - Where may I start? - What is the packaging/release process and how can one help become a package maintainer? - Advise on legal stuff around publishing of rpms (the noredist repositories bundle non-oss jar dependencies such as those from Vmware vim sdk etc)? - How can the packages also be available for Fedora, may RHEL and derivatives? - Thoughts, comments? Thanks. Regards. [1] https://cloudstack.apache.org/ [2] https://wiki.centos.org/SpecialInterestGroup/Cloud [3] packages.shapeblue.com/cloudstack/upstream [4] CloudStack packaging, spec files etc: https://github.com/apache/cloudstack/tree/master/packaging

3 4

[Cloud SIG] Reboot weekly Cloud SIG meetings
by Haïkel 22 Feb '18

22 Feb '18

Hi, since we have a newer group (CloudStack) joining us, we decided to reboot our weekly meetings. In order to find a timeslot that suits everyone, I suggest that we use a whenisgood poll: http://whenisgood.net/bpqn4fn Please don't forget to set your timezone when answering the poll. I'll publish results asap Regards, H.

4 7

[opstools] Building opstools7-fluentd-012-release for ppc64le
by Mark Hamzy 22 Feb '18

22 Feb '18

Hey y'all, So what scripts/process builds the group of rpms for the tag opstools7-fluentd-012-release? I would like to build them for ppc64le. So the packages in http://mirror.centos.org/centos/7/opstools/x86_64/ Would end up mirror.centos.org/altarch/7/opstools/ppc64le/ Is this something I could help with? -- Mark You must be the change you wish to see in the world. -- Mahatma Gandhi Never let the future disturb you. You will meet it, if you have to, with the same weapons of reason which today arm you against the present. -- Marcus Aurelius

3 3

CentOS PaaS SIG meeting (2018-02-21)
by Troy Dawson 21 Feb '18

21 Feb '18

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

1 0

php71 build targets
by Charles A. Plater 21 Feb '18

21 Feb '18

I’m trying to figure out how build targets are requested / added to the Software Collections, specifically php71 and php71-fpm. Currently, the php71 RPMs are available for RHEL7 and CentOS7. What is the process to request these RPMs to be added to the CentOS6 (and potentially RHEL6) Software Collection? Many thanks in advance. -- Charles Plater Lead Application Technical Analyst Internet Services +1-313-577-4620 ab3189(a)wayne.edu

2 1

Re: [CentOS-devel] Vagrant / Centos 7 Install Error: Cannot find a valid baseurl for repo: base/7/x86_64
by Simon Payne 21 Feb '18

21 Feb '18

Hi Laurentiu, Thank you very much for trying it out and giving your feedback. I will have a look at some of those other options. Cheers Simon Message: 11 > Date: Tue, 20 Feb 2018 20:45:36 +0100 > From: Laurentiu Pancescu <lpancescu(a)centosproject.org> > To: centos-devel(a)centos.org > Subject: Re: [CentOS-devel] Vagrant / Centos 7 Install Error: Cannot > find a valid baseurl for repo: base/7/x86_64 > Message-ID: <abbbfc72-9579-462f-dff2-6bab7ee6ecf8(a)centosproject.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Simon, > > On 20/02/18 12:01, Simon Payne wrote: > > I am trying to get a Centos VM working with Vagrant + VirtualBox on > Windows > > 8. However I'm getting an error to do with the centos/7 box. > > > > I have installed Vagrant using its automated installer, and VirtualBox, > and > > downloaded this box: > > > > https://app.vagrantup.com/centos/boxes/7 > [snip] > > Cannot find a valid baseurl for repo: base/7/x86_64 > > > > I don't know how to fix it. I append the error trace and my Vagrantfile. > > Any help will be appreciated. > > I'm not sure what's going on,either. VirtualBox users on Windows have > been plagued by DNS problems immediately after centos/7 boots (disabling > the NAT DNS resolver is an attempt to work around that). I tried to > simulate that by disabling the host networking immediately after running > "vagrant up", and that produces the same error message you got. > > I don't have access to Windows, so I ran your example on a Mac with > VirtualBox 5.2.6, vagrant-vbguest 0.15.1 and centos/7 1801.02. It > installed the guest additions and mounted the shared folder via vboxsf. > The DNS resolver problems were always restricted to VirtualBox on > Windows - it works on Mac and Linux, as do all other hypervisors. I'm > afraid I can't help you; perhaps you can try to use our Hyper-V images > (Hyper-V is included for free in Windows Professional and higher) or > VMware, if that's an option. > > Please note that the guest additions aren't really needed. Networking > works just fine without them, and you can use Samba or vagrant-sshfs for > sharing files: > > https://github.com/dustymabe/vagrant-sshfs > > Best regards, > Lauren?iu >

1 0

Vagrant / Centos 7 Install Error: Cannot find a valid baseurl for repo: base/7/x86_64
by Simon Payne 20 Feb '18

20 Feb '18

Hello, I am trying to get a Centos VM working with Vagrant + VirtualBox on Windows 8. However I'm getting an error to do with the centos/7 box. I have installed Vagrant using its automated installer, and VirtualBox, and downloaded this box: https://app.vagrantup.com/centos/boxes/7 here is the output of that: D:\Vagrant>vagrant box add centos/7 ==> box: Loading metadata for box 'centos/7' box: URL: https://vagrantcloud.com/centos/7 This box can work with multiple providers! The providers that it can work with are listed below. Please review the list and choose the provider you will be working with. 1) hyperv 2) libvirt 3) virtualbox 4) vmware_desktop Enter your choice: 3 ==> box: Adding box 'centos/7' (v1801.02) for provider: virtualbox box: Downloading: https://vagrantcloud.com/centos/boxes/7/versions/1801.02/providers/virtualb… box: Progress: 100% (Rate: 950k/s, Estimated time remaining: --:--:--) ==> box: Successfully added box 'centos/7' (v1801.02) for 'virtualbox'! So I did a vagrant init, ran "vagrant up" and I got a warning about VB guest additions needed, so I ran this command: vagrant plugin install vagrant-vbguest D:\Vagrant>vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Fetching: micromachine-2.0.0.gem (100%) Fetching: vagrant-vbguest-0.15.1.gem (100%) Installed the plugin 'vagrant-vbguest (0.15.1)'! I then tried "vagrant up" again but got this error: Cannot find a valid baseurl for repo: base/7/x86_64 I don't know how to fix it. I append the error trace and my Vagrantfile. Any help will be appreciated. thanks, Simon Appendages... ERROR TRACE ============= D:\Vagrant>vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'centos/7' is up to date... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 80 (guest) => 8080 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key ==> default: Machine booted and ready! [default] No installation found. Loaded plugins: fastestmirror One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! yum install -y kernel-devel-`uname -r` gcc binutils make perl bzip2 Stdout from the command: Loaded plugins: fastestmirror Stderr from the command: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 MY VAGRANTILE ============== # -*- mode: ruby -*- # vi: set ft=ruby : # All Vagrant configuration is done below. The "2" in Vagrant.configure # configures the configuration version (we support older styles for # backwards compatibility). Please don't change it unless you know what # you're doing. Vagrant.configure("2") do |config| # The most common configuration options are documented and commented below. # For a complete reference, please see the online documentation at # https://docs.vagrantup.com. # Every Vagrant development environment requires a box. You can search for # boxes at https://vagrantcloud.com/search. config.vm.box = "centos/7" # Disable automatic box update checking. If you disable this, then # boxes will only be checked for updates when the user runs # `vagrant box outdated`. This is not recommended. # config.vm.box_check_update = false # Create a forwarded port mapping which allows access to a specific port # within the machine from a port on the host machine. In the example below, # accessing "localhost:8080" will access port 80 on the guest machine. # NOTE: This will enable public access to the opened port # config.vm.network "forwarded_port", guest: 80, host: 8080 # Create a forwarded port mapping which allows access to a specific port # within the machine from a port on the host machine and only allow access # via 127.0.0.1 to disable public access config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1" # Create a private network, which allows host-only access to the machine # using a specific IP. # config.vm.network "private_network", ip: "192.168.33.10" # Create a public network, which generally matched to bridged network. # Bridged networks make the machine appear as another physical device on # your network. # config.vm.network "public_network" # Share an additional folder to the guest VM. The first argument is # the path on the host to the actual folder. The second argument is # the path on the guest to mount the folder. And the optional third # argument is a set of non-required options. # config.vm.synced_folder "./data", "/vagrant_data" # Provider-specific configuration so you can fine-tune various # backing providers for Vagrant. These expose provider-specific options. # Example for VirtualBox: # config.vm.provider "virtualbox" do |vb| # # Display the VirtualBox GUI when booting the machine # vb.gui = true # # # Customize the amount of memory on the VM: # vb.memory = "1024" vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"] end # # View the documentation for the provider you are using for more # information on available options. # Enable provisioning with a shell script. Additional provisioners such as # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the # documentation for more information about their specific syntax and use. # config.vm.provision "shell", inline: <<-SHELL # apt-get update # apt-get install -y apache2 # SHELL config.vm.synced_folder ".", "/vagrant", type: "virtualbox" end

2 1

CentOS for IBM Mainframes.
by Javier Romero 20 Feb '18

20 Feb '18

Hi all, I see that IBM LinuxONE, provides a Z Mainframe running with Linux Red Hat, SUSE OR Ubuntu Server distros. Do you think that could also be useful for CentOS to be another option for LinuxONE? Maybe a a CentOS Mainframe SIG can be created to work on this. Thanks for your attention. Regards, Javier Romero

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2018