similar to: Updated Vagrant Box's are now available : 1607

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7/x86_64 and for the first time for CentOS Linux 6/x86_64; We are providing box's for Livbirt provider and the Virtual Box provider. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available, as in the past, for the Libvirt and the VirtualBox providers in Vagrant. We have also enabled the vmware providers, for anyone using Vmware's products for backing Vagrant on Linux, MacOS or Windows. ref:

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

I'm using libvirt on Debian/stretch (testing) with vagrant and the vagrant-libvirt plugin. When I import a vagrant box (jessie64.box), the resulting file permssions let anyone in the "kvm" group read the img. But when I build upon that box, only root can read it: -rw------- 1 root root 20198785024 Sep 19 18:19 buildserver_default.img -rwxr--r-- 1 libvirt-qemu kvm

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

Hi, I have a fresh CentOS 5.8 Vagrant VM that I''m using to emulate a customer''s server. During the first Puppet run, it takes 13 minutes and 48 seconds to sync the Puppet Labs stdlib module. On a similar Ubuntu 12.04.1 Vagrant VM, Puppet starts up, and almost instantly goes from plugin sync to facter load. Is this load time for stdlib on a RHEL variant normal?

CentOS Errata and Bugfix Advisory 2015:1607 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1607.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0ed4821988991aa93de0154010825fe54f8e2e79370e2ab7f4f74ba659df8238 dovecot-2.0.9-19.el6.1.i686.rpm

CentOS Errata and Bugfix Advisory 2017:1607 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1607.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 87ae485753769dfb65699bbed13b87b4de3dbd0cacc3feeda3913efd7e1fffec xfsprogs-4.5.0-10.el7_3.i686.rpm

Hello, Strangely, the profile sync error is gone now on that machine. But just to be safe, we're rejecting the 1607 updates with our WSUS. It will give me more time to investigate the problem. We'll probably sticking with 1511 in our teaching labs until summer 2017. Sorry I can't help more... Cheers, Luc. Le 2016-09-19 16:30, Bob of Donelson Trophy via samba a écrit : > On

Hello, all! Suddenly, after upgrading of my FreeBSD-Stable box I got message from VMWare: VMware Workstation PANIC: BUG F(571):1607 bugNr=2302. Anybody can help me to fix this bug? (I tryed back to 4.8-release but it didn't help ...) Best regards, Anatoliy Dmytriyev

Hello folks, We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. Before I search the event logs or provide details, has anyone experience profile sync wierdness? They changed the profile version again... in 1511 it is version 5, in 1607 it is now version 6. Thank You! -- Luc Lalonde, analyste

On 2016-09-19 14:08, Marcio Vogel Merlone dos Santos via samba wrote: > Em 09/09/2016 12:48, Luc Lalonde via samba escreveu: > >> We have some machines that have updated to the Windows 10 anniversary update (1607) that are having roaming profile sync problems. >> >> Before I search the event logs or provide details, has anyone experience profile sync wierdness? >>

https://bugzilla.mindrot.org/show_bug.cgi?id=1607 Summary: compile errors buliding OpenSSH for older Red Hat Product: Portable OpenSSH Version: 5.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org