We have released the Atomic Developer Bundle 1.8.0 through CentOS
Atomic SIG.
The ADB release also includes release of following ecosystem projects:
* vagrant-service-manager 1.0.0 : A Vagrant plugin designed to provide
an interface between ADB and the user's development environment and for
easier access to the features and services provided by the ADB.
* adb-utils 1.4 : A set of utility scripts and configuration files for ADB.
ADB 1.8.0 release release adds new feature and several bugfixes, including:
- Added fuse-sshfs to the ADB box. This adds the support for
vagrant-sshfs to ADB [5].
- Enhancement to ansible playbook for Mesos Vagrantfile.
adb-utils 1.4 release includes several bugfixes, including
- Create OpenShift sample-project as vagrant user without
$KUBECONFIG set.
- Fixes to OpenShift image stream.
- Changes to use new OpenShift Origin docker images i.e. tag 1.1.3.
vagrant-service-manager 1.0.0 release adds several new features, including:
- New sub-command `restart` for restarting services in the box
- Shows correct command for exporting env variables in cygwin
environment
- New IP detection routine fixing IP detection for libvirt provider
- Simplified help text and help option per sub-command
- Plugin is backward compatible with docker 1.8.2
- Fixed defaults for configuring OpenShift service in CDK box
Known issues:
* Running AtomicApp in ADB fails. Refer:
https://github.com/projectatomic/adb-atomic-developer-bundle/issues/329
* Following workaround can be used till the above issue is fixed.
$ sudo -E atomic run projectatomic/helloapache
This release also includes many smaller changes and bugfixes, which are
detailed in the release changelog from adb-utils [1],
vagrant-service-manager [2] and ADB [3]
Please update the ADB Vagrant box [4] and the vagrant-service-manager to
1.0.0 ($ vagrant plugin update vagrant-service-manager) and give the new
ADB a spin.
[1] https://github.com/projectatomic/adb-utils/releases/tag/v1.4
[2]
https://github.com/projectatomic/vagrant-service-manager/releases/tag/v1.0.0
[3]
https://github.com/projectatomic/adb-atomic-developer-bundle/releases/tag/v…
[4]
https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do…
[5]
https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do…
_______________________________________________
Container-tools mailing list
Container-tools(a)redhat.com
https://www.redhat.com/mailman/listinfo/container-tools
Hi,
the RDO community has packages available for Mitaka Stable in its
testing repositories.
Official RDO release will be announced after we validate this release
with our CI.
Regards,
H.
Hi,
It is now time for sig-configmanagement member to discuss and open bug
requests on bugs.centos.org about CBS tag requests.
CBS: https://wiki.centos.org/HowTos/CommunityBuildSystem
How to: https://wiki.centos.org/HowTos/CentosPackager
Bug requests to create new tags need to be open under the buildsys
category.
This is the bug request I opened for Puppet and common tags:
https://bugs.centos.org/view.php?id=10604
I would also like that any member plays with CBS by trying to make
scratch builds to CBS. I encourage you to make scratch builds in the "bananas" tags.
! Please ask for help it anything is not clear. It would be great if as
much people could test CBS before the next meeting and ask for tags.
--
(o- Julien Pivotto
//\ Config Management SIG
V_/_ https://frama.link/cfgmgmt
Hi all,
For the Config Management SIG, we will need to rebuild some EPEL
packages. However, we do not want to rebuild them 'as it' because we do
not want to depend on EPEL version etc. EPEL is not always "stable" and
we do not want our users to be in troubles regarding EPEL decisions
(https://lists.centos.org/pipermail/centos-devel/2015-December/014101.html)
Some projects use Python or Ruby librairies that we could also put in a
SCL.
What prefix should we use for those SCL?
Some ideas:
/opt/centos/
/opt/centos-sig-configmanagement
/opt/centos/sig-configmanagement
Thanks for your feedback.
--
(o- Julien Pivotto
//\ Config Management SIG
V_/_ https://frama.link/cfgmgmt
Hi,
I was expecting the SIG meetings to be shifted by one hour due to DST.
However, that is not possible because the pass-sig meetings are not DST
affected.
I will NOT be able to join the next meeting, because I was expecting it
to be held one hour earlier.
The date of the next meeting is:
date -d 'Wed Apr 13 16:00:00 UTC 2016'
(Wed Apr 13 18:00:00 CEST 2016)
Another member of the sig will need to take the lead of the meeting.
--
(o- Julien Pivotto
//\ Config Management SIG
V_/_ https://frama.link/cfgmgmt
Hello,
It's time for our weekly PaaS SIG sync-up meeting
Time: 1500 UTC - Wedensdays
Date: Today Wedensday, 06 April 2016
Where: IRC- Freenode - #centos-devel
Agenda:
- OpenShift Current Status
-- rpms - origin 1.1.6, docker 1.9.1-origin
-- repo(s)
--- https://tdawson.fedorapeople.org/centos/CentOS-OpenShift.repo
--- testing (buildlogs)
--- candidate
-- images - not started
-- Quickstart - not started
- What is our criteria for a release?
- Building image demo ??
- Open Floor