[SSSD] [PATCH] Add Vagrant configuration for SSSD

Stephen Gallagher sgallagh at redhat.com
Mon Jun 1 16:54:07 UTC 2015


On Mon, 2015-06-01 at 14:24 +0200, Lukas Slebodnik wrote:
> On (01/06/15 08:01), Stephen Gallagher wrote:
> > On Wed, 2015-05-27 at 15:54 -0400, Stephen Gallagher wrote:
> > > On Wed, 2015-05-27 at 21:36 +0200, Lukas Slebodnik wrote:
> > > > On (27/05/15 15:30), Stephen Gallagher wrote:
> > > > > On Wed, 2015-05-27 at 13:31 -0400, Stephen Gallagher wrote:
> > > > > > To set up a Vagrant development environment:
> > > > > > * Install the Vagrant packages for your development system
> > > > > >   * On Fedora 22 and later: 'dnf install vagrant-libvirt'
> > > > > > * Deploy the Vagrant box:
> > > > > >   * 'vagrant up'
> > > > > > * Build SSSD:
> > > > > >   * vagrant ssh -c "cd /vagrant; reconfig; chmake"
> > > > > > 
> > > > > > Vagrant can keep your development tree in-sync with the 
> > > > > > Vagrant 
> > > > > > 
> > > > > > box
> > > > > > by running 'vagrant rsync-auto' in a shell (this will 
> > > > > > continue 
> > > > > > to
> > > > > > run, monitoring for changes and syncing them as they are 
> > > > > > saved).
> > > > > > Alternately, it can be manually synced with 'vagrant rsync' 
> > > > > > at 
> > > > > > will.
> > > > > 
> > > > > One minor update; added a few more packages to the deployment
> > > > > installation (adcli, oddjob-mkhomedir and polkit) to support 
> > > > > realmd.
> > > > 
> > > > > From a652a5ea9233b1cac6a84b205a4e71cc9b659aaf Mon Sep 17 
> > > > > 00:00:00 
> > > > > 
> > > > > 2001
> > > > > From: Stephen Gallagher <sgallagh at redhat.com>
> > > > > Date: Wed, 27 May 2015 13:17:40 -0400
> > > > > Subject: [PATCH] Add Vagrant configuration for SSSD
> > > > > 
> > > > > To set up a Vagrant development environment:
> > > > > * Install the Vagrant packages for your development system
> > > > >  * On Fedora 22 and later: 'dnf install vagrant-libvirt'
> > > > > * Deploy the Vagrant box:
> > > > >  * 'vagrant up'
> > > > > * Build SSSD:
> > > > >  * vagrant ssh -c "cd /vagrant; reconfig; chmake"
> > > > > 
> > > > > Vagrant can keep your development tree in-sync with the 
> > > > > Vagrant 
> > > > > box
> > > > > by running 'vagrant rsync-auto' in a shell (this will 
> > > > > continue to
> > > > > run, monitoring for changes and syncing them as they are 
> > > > > saved).
> > > > > Alternately, it can be manually synced with 'vagrant rsync' 
> > > > > at 
> > > > > will.
> > > > > ---
> > > > > Vagrantfile          | 74 
> > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > > > vagrant/bootstrap.sh | 21 +++++++++++++++
> > > > Could it be in contrib directory?
> > > > 
> > > 
> > > Well, bootstrap.sh could be, I suppose. Unfortunately, 
> > > "Vagrantfile"
> > > must always be in the root of the source tree.
> > 
> > 
> > Sorry, this response failed to ask: Is this a nack? Do you want me 
> > to
> > move the bootstrap.sh file and resubmit it?
> I would prefer to do not polute git root directory.
> Vagrantfile can stay there but bootstrap.sh
> could be in contrib (contrib/vagrant ...)
> 
> It would be also good to add link to blog post
> http://fedoramagazine.org/running-vagrant-fedora-22/
> to the comment. So I needn't to look it uo every time :-)
> 
> IMHO it's quite good explanation of vagrant on fedora
> 

Updated patch attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-Vagrant-configuration-for-SSSD.patch
Type: text/x-patch
Size: 5606 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20150601/a1738ecd/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20150601/a1738ecd/attachment.sig>


More information about the sssd-devel mailing list