devel

devel@lists.centos.org

4687 discussions

Vagrant images for Hyper-V
by Patrick Lang 02 May '17

02 May '17

> > > > We now have a working solution for producing regular .vhd images as part > > of our release process: CBS is now using qemu-img-ev and qemu-kvm-ev from > > the Virt SIG, instead of the versions in CentOS Linux base. We don't need > > either VirtualBox or changes in Image Factory. > > > > If anyone has access to Hyper-V on Windows and would be willing to test > > two Vagrant images, please let me know. I received conflicting test > > results from Thomas and Michael, and I'd like to have at least an > > additional test before deciding whether to release them or not. > > > > Thanks, > > Lauren?iu > > > > I just reached out to a friend on the Hyper-V team at MS to see if we can > figure something out. It would be nice to have a way to automate this > testing going forward. > > -Jeff I emailed Laurentiu off list to get the boxes for 6.1.1 and 7.1.1. I'm late to joining this discussion but I'm happy to help. I work on the Hyper-V team and have been doing some testing and improvements to Vagrant and Packer on the side. re: sparse files - NTFS doesn't support sparse files, but Hyper-V does have dynamically expanding VHD and VHDX files. VHDX allocations are configurable but the default of 32MB is tuned to NTFS which puts all metadata at the beginning of the disk. Dropping VHDX allocations down to 1MB helps reduce the slack space left after each inode. VHD uses smaller allocations so it’s less of an issue. Both images are just over a gig on disk which is about what I’d expect. If you’re optimizing the template Vagrantfiles in the boxes, it would be very helpful to add differencing_disk = true to avoid copying the full VHD and reduce IO in vagrant up. Here's what I observed on each image Centos 6.1.1 - Vagrant didn't find an IP address upon bootup. I logged in via the console and the Hyper-V virtual NIC was on eth1 which didn't have dhclient configured. I ran dhclient manually, then vagrant ssh was able to find the IP Centos 7.1.1 - Vagrant worked as expected. It found the IP as the VM booted up. I haven't fully tested everything but wanted to share some of the results. Let me know if there's a list of tests run against the other boxes and I can go through them. Cheers, Patrick Lang (github.com/patricklang) Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

2 4

We need a newer Vagrant in SCL
by Laurentiu Pancescu 02 May '17

02 May '17

Hello, Our cico test for testing our Vagrant images have support for optionally using vagrant-vbguest. This is now failing with: + scl enable sclo-vagrant1 'vagrant plugin install vagrant-vbguest' Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: Authentication is required for http://gems.hashicorp.com/. Please supply credentials for this source. You can do this by running: bundle config http://gems.hashicorp.com/ username:password Build step 'Execute shell' marked build as failure I think this is caused by the older version we have in SCL - I can install vagrant-vbguest without any issues on Vagrant 1.9.3 (on OS X). I now reverted the test to not use vagrant-vbguest, but it's still failing because SCL Vagrant doesn't support VirtualBox 5.1.x. Oracle already put a warning on the download page for VirtualBox 5.0.x: "VirtualBox 5.0.x runs out of support, switch to VirtualBox 5.1.x!" https://www.virtualbox.org/wiki/Download_Old_Builds_5_0 We risk becoming unable to automatically test our images with VirtualBox - could we get a Vagrant update in SCL, please? Thanks, Laurentiu

3 4

SIG Proposal - High performance computing (HPC) SIG
by Ondřej Vašík 01 May '17

01 May '17

Hi, I would like to propose start of High performance computing (HPC) SIG. I see it already mentioned on https://wiki.centos.org/SpecialInterestGroup among Future SIGs. Primary reason for the SIG existence will be to improve the state of High performance computing related packages on CentOS and similar distributions, with special focus on stability of builds, CentOS (and similar distribution) related improvements for OpenHPC project and getting new HPC packages packaged for CentOS and/or Fedora. Initial members would be me (ovasik(a)redhat.com, CentOS FAS account: Reset), Adrian Reber (areber(a)redhat.com, CentOS FAS account: areber), Stanislav Kozina (skozina(a)redhat.com, CentOS FAS account: ersin) and Jan Chaloupka (jchaloup(a)fedoraproject.org, CentOS FAS account: jchaloup). Of course, anyone is welcome to join. Thanks in advance for approving/sponsoring the SIG. Regards, Ondrej Vasik

7 9

GA Release: CentOS Community Container Pipeline
by Bamacharan Kundu 28 Apr '17

28 Apr '17

Hi All, We would like to welcome and introduce you all to the CentOS Community Container Pipeline Service[1][4]. This is an effort to make the developer's life simple for containerizing open source projects, where the developer can develop applications on a stack (django, golang, nodejs, redis, rabbitmq, etc.) of his/her choice using CentOS as the base platform. For every open source project building their container images using CentOS Community Container Pipeline, the service ensures that the application is packaged into a container and updated automatically every time changes are pushed to the Git (GitHub, BitBucket, Gitlab, etc.) repository. The resulting container image is scanned for updates, fixes, capabilities, and delivered to registry.centos.org[3]. From there anyone can pull it and run the application. Pipeline service rebuilds and image when an RPM package is updated in the container or base image is updated. For using the service to build the images please raise a PR in container-index [2] All the currently available images at registry.centos.org are updated at Container Pipeline Wiki[3] We're always looking for ideas and improvements for the service. If you're interested in contributing to this repository, here[1] is the source code for the service. For any queries get in touch with us on #centos-devel IRC channel on Freenode or send a mail to centos-devel(a)centos.org. Regards Bama Charan Kundu [1] https://github.com/CentOS/container-pipeline-service [2] https://github.com/centos/container-index [3] https://wiki.centos.org/ContainerPipeline [4] http://www.rtnpro.com/centos-community-container-pipeline/

2 1

The status of our Vagrant images for Hyper-V
by Laurentiu Pancescu 26 Apr '17

26 Apr '17

Hi there, I created the first experimental Vagrant images for Hyper-V on March 14, after the CBS upgrade. They seem to be functional, but they generate a lot of disk I/O during "vagrant up", according to Thomas and Michael. I think we end up with 40GB files as disk images - this is the maximum size of the virtual hard drives we create, but most of that is empty. I compared the contents of our box file to the one from kozo/centos-7, which is produced natively using Packer and Hyper-V: our image contains a real 40GB disk image, while the kozo image only has a 2.1GB image. Image Factory converts the KVM .qcow2 image to a .vhd by calling "qemu-img convert -O vpc <source> <destination>". This produces a 40GB sparse file taking just 1.1GB of space (both with the fixed and dynamic subformats). The problem occurs while packing the sparse image into the .box file: Python's tarfile module only has read-only support for sparse files (a GNU tar extension) - even in Python 3, so the archive ends up with a regular 40GB file. Creating 40GB sparse files seems to be specific to qemu-img: "VBoxManage convertmedium disk box.vmdk box.vhd" produces a 1.1GB regular file (VirtualBox' convert tool doesn't seem to support QCOW2, so I had to first convert the QCOW2 image to VMDK). We should probably either: - call GNU tar from Image Factory to preserve the sparseness of our image files (and hope that Windows handles them properly) - use VBoxManage to convert to .vhd (VirtualBox is not in our repos, but Oracle offers a .rpm for EL7 systems). In the mean time, we will probably release v1703 without Hyper-V support, since CentOS Linux 6.9 was already released. Best regards, Laurențiu [vagrant@localhost ~]$ tar -tvzf c7.box # that's ours drwxr-xr-x root/root 0 2017-03-14 11:23 Virtual Machines/ -rw-r--r-- root/root 39100 2017-03-14 11:23 Virtual Machines/vm.XML -rw-r--r-- root/root 114 2017-03-14 11:23 Vagrantfile drwxr-xr-x root/root 0 2017-03-14 11:22 Virtual Hard Disks/ -rwxr-xr-x root/root 42949672960 2017-03-14 11:23 Virtual Hard Disks/disk.vhd -rw-r--r-- root/root 22 2017-03-14 11:23 metadata.json [vagrant@localhost ~]$ unzip -l hyperv.box # kozo/centos-7 Archive: hyperv.box.zip Length Date Time Name --------- ---------- ----- ---- 36898 02-25-2017 13:05 Virtual Machines/1BF518E8-0055-4ABF-8750-E1D703B23A47.vmcx 61440 02-25-2017 13:05 Virtual Machines/1BF518E8-0055-4ABF-8750-E1D703B23A47.VMRS 64 02-25-2017 12:47 metadata.json 2185232384 02-25-2017 13:05 Virtual Hard Disks/CentOS7.vhdx --------- ------- 2185330786 4 files

4 7

CentOS PaaS SIG meeting (2017-04-26)
by Troy Dawson 26 Apr '17

26 Apr '17

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

1 1

OpenShift Origin 1.5.0 in testing
by Troy Dawson 25 Apr '17

25 Apr '17

Hi All, The GA released Origin 1.5.0 has been built and is in the Paas testing areas. https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin/ https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin15/ To install/update the packages via yum, you should be able to use the centos-openshift-origin-testing repo, that is disabled by default. yum --enablerepo=centos-openshift-origin-testing list origin We also have the update ansible (2.2.2.0) and openshift-ansible (3.5.58) in those testing repo's as well. Please test. We'd like to get these pushed to release by the end of the week. Troy

1 0

OpenStack Cinder 9.1.4
by Oisin O'Malley 24 Apr '17

24 Apr '17

Hi All, OpenStack Cinder 9.1.4 has been released as part of the Newton release cycle. If not already in progress, could we see packages released for Cinder 9.1.4. Currently only 9.1.2 is available in the Newton repo. We are affected by a NetApp driver bug that was fixed upstream in the 9.1.4 release; https://bugs.launchpad.net/cinder/+bug/1660870 Regards, Oisin Oisin O'Malley Systems Engineer Iocane Pty Ltd 763 South Road Black Forest SA 5035 Office:+61 (8) 8413 1010 Fax:+61 (8) 8231 2050 Email:oisin.omalley@iocane.com.au Web:www.iocane.com.au Better for business

2 1

Stable Wine packages for CentOS 7
by Toni Spets 23 Apr '17

23 Apr '17

Hello, I think there are quite some potential Wine users for C7 that would like working packages that can actually run Windows programs over EPEL 64-bit only build. Here's my Copr project for Wine 2.0 stable series that includes complete i686-only packages for x86_64 CentOS 7: https://copr.fedorainfracloud.org/coprs/hifi/wine-backport/ At this point it does *not* depend on EPEL so you can install them on a clean CentOS 7 x86_64 system. Please do note the description for features that differ from Fedora Wine packages. Hope someone finds these useful. Thanks! -- Toni Spets

1 0

Missing GlusterFS in 32-bit
by Zdenek Sedlak 20 Apr '17

20 Apr '17

Hi, do you know why gluster* packages are excluded in i386 as mentioned here: http://people.centos.org/hughesjr/missing-actual-i686-filenames.txt //Zdenek

3 4

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