Hi Jason,
Is there any change to release CentOS Atomic Host?
Last release was made more than 2 month ago and consist of alpha version of
kubernetes/
Regards,
Eduard
A new OpenStack provider for the sclo-vagrant1 collection is available
for testing in the centos-sclo-sclo-testing repository.
To install it, run:
yum install centos-release-scl
yum install --enablerepo=centos-sclo-sclo-testing
sclo-vagrant1-vagrant-openstack-provider
It can be used by running:
scl enable sclo-vagrant1 "vagrant up --provider=openstack"
and documentation is available for the provider in the -doc RPM or from
https://github.com/ggiamarchi/vagrant-openstack-provider.
Please provide feedback if you have it, else I'll push to the stable
repo in a week or so.
Kind regards,
--
Dominic Cleal
dominic(a)cleal.org
New packages built and tagged:
sclo-php54-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm
sclo-php55-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm
sclo-php56-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm
sclo-php54-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm
sclo-php55-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm
sclo-php56-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm
These packages extend the php54, php55 and rh-php56 collections,
and are available now in centos-sclo-sclo-testing repostiory.
Feedback welcome.
These packages will be push in stable repository in a few weeks if no
bugs are reported.
P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo
Hi all,
Here is the update for work recently done for the CentOS Community
Container Pipeline.
- Docker builds in the CCCP-Service were taking a long time for building
each images. We tracked down the issue and got in conclusion of building
the images sequentially. This increase the performance as the other option
of creating docker lvm pool is already in place.
-
- For getting the builds sequential we created beanstalkd tubes managing
the builds from jenkins. Jenkins pushes all the builds to beankstalkd tube.
beanstalk client starts the build one after another is complete.
- We were checking with the facts to include OSBS as build client for
CCCP. After analyzing different facts of benefits of osbs and our current
issues for the system, we are postponing OSBS adoption till our first
release. We will be looking for adopting this after that.
-
- We got atomic registry built from CCCP-Service with proper namespace.
This is also demoed as end to end user story to the team. Currently we are
taking the origin base images from outside of registry.centos.org
In the coming days, we will be focusing on :
- Getting Openshift origin completely built from registry.centos.org
with all its base images (also indirectly solving problem with dependent
container images)
- Write a wiki page on wiki.centos.org for atomic registry.
- Setting up end to end delivery with test suites (container scanning
etc) and build sequence.
*Mohammed Zeeshan Ahmed*
Associate Software Engineer,
Redhat Developers Team (Devtools)
IRC : mzee1000
mohammedzee1000.wordpress.com
Old PGP Public Key :
http://pgp.mit.edu/pks/lookup?op=get&search=0x726A119E62847E37 (REVOKED)
New PGP Public Key :
https://pgp.mit.edu/pks/lookup?op=get&search=0x147A8569AFC5E9ED
On 16/06/16 10:14, Honza Horak wrote:
> I've tried the new package and it looks good, it does everything it
> should from my PoV.
Thanks for testing, I've tagged it for release.
--
Dominic Cleal
dominic(a)cleal.org
There were discussions on irc about it but I lost track of who I should
speak with etc so decided to write to mailing list instead.
The goal is to rebuild OpenStack 'mitaka' packages for AArch64 (AltArch)
in CBS (there is one builder for this architecture).
Question is how to make it in best way?
One of ideas was:
1. create new tag (cloud7-openstack-mitaka-candidate-aarch64?)
2. import all 'noarch' builds from cloud7-openstack-mitaka-* tags
3. send all required packages to the builder
4. test resulting packages
5. import/merge all of them to proper cloud7-openstack-mitaka-* tag
Other was about doing scratch builds and merging them with x86-64 ones.
How we can proceed? I think that first idea is good as it allows us to
do builds without touching x86-64 tag before we are ready for merging.
But I do not have koji experience so may be wrong.
Hello,
It's time for our weekly PaaS SIG sync-up meeting
Time: 1700 UTC - Wedensdays
Date: Today Wedensday, 15 June 2016
Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms
--- origin 1.2.0 - now in stable repo
-- Automated testing
-- images / image building
-- Documentation
--- Need openshift-ansible in centos repo for quickstart - progress?
- Automated rpm building
- Open Floor
Minutes from last meeting:
https://www.centos.org/minutes/2016/may/centos-devel.2016-05-25-17.00.log.h…
Honza,
Can you set centos-release-scl-rh (or if more appropriate,
centos-release-scl) to obsolete centos-release-SCL in CentOS-6. I have
removed the old SCL/ repo in 6.8 and you have newer versions of all
packages.
Thanks,
Johnny Hughes
Hi all,
I noticed that there are centos 7 cloud images for x86. But i did not
find the cloud images for ppc64le. Are there any work on it within this
community? Or is there any plan to work on it?
Regards,
Xiandong Meng <mengxiandong(a)gmail.com>
mengxiandong(a)gmail.com