keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
94ee42b03b
rpm-ostree/vagrant/setup.yml

67 lines
2.9 KiB
YAML
Raw Normal View History

tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon
2016-06-04 17:48:06 +03:00
---
- hosts: all
setup.yml: cache buildimg container By far the longest step in provisioning a new VM is the building of the container. This helps alleviate things a little by caching it on the host. It's not a complete solution however. We also need to make it easy to update an existing container. Closes: #344 Approved by: cgwalters
2016-06-22 19:00:45 +03:00
gather_facts: no
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon
2016-06-04 17:48:06 +03:00
become: yes
tasks:
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
- name: generate config
Vagrantfile: specify full path to using_sshfs When running `vagrant ssh-config` from ansible, Vagrant for some reason still wants to execute the File.write() operation, but fails to do so because the $PWD is $topsrcdir/vagrant, in which .vagrant does not exist. Switch to using the absolute path. Closes: #555 Approved by: cgwalters
2016-12-21 07:18:38 +03:00
local_action: shell vagrant ssh-config > ../ssh-config
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
become: no
vagrant: generate ssh-config We further split libvm from vagrant. It no longer does 'vagrant ssh-config'. Instead, it always assumes that an ssh-config is provided. We now have complete separation of libvm from vagrant. We change the ansible provisioner as follows: - Allow passing in a VAGRANT_BOX env var to override the default CentOS box. - No longer assume that the root user account is unlocked and has a valid 'vagrant' password. This worked for the centos box but isn't sure to work on every box. Instead, we now just run ansible as the default vagrant user, and during provisioning set up the root account and generate an ssh-config so that libvm can connect directly as root. - No longer build the buildimg during provisioning. This actually stopped working a while ago since the default rsync is disabled. We can just let the buildimg get created on the first compilation. In practice, the bigger issue isn't creating the buildimg, but being able to easily update the host and buildimg pkgs. Closes: #516 Approved by: jlebon
2016-10-31 23:26:56 +03:00
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
# The test suite requires direct ssh to root.
vagrant: generate ssh-config We further split libvm from vagrant. It no longer does 'vagrant ssh-config'. Instead, it always assumes that an ssh-config is provided. We now have complete separation of libvm from vagrant. We change the ansible provisioner as follows: - Allow passing in a VAGRANT_BOX env var to override the default CentOS box. - No longer assume that the root user account is unlocked and has a valid 'vagrant' password. This worked for the centos box but isn't sure to work on every box. Instead, we now just run ansible as the default vagrant user, and during provisioning set up the root account and generate an ssh-config so that libvm can connect directly as root. - No longer build the buildimg during provisioning. This actually stopped working a while ago since the default rsync is disabled. We can just let the buildimg get created on the first compilation. In practice, the bigger issue isn't creating the buildimg, but being able to easily update the host and buildimg pkgs. Closes: #516 Approved by: jlebon
2016-10-31 23:26:56 +03:00
- file: state=directory mode=0600 path=/root/.ssh
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
- copy: remote_src=True src=/home/vagrant/.ssh/authorized_keys dest=/root/.ssh/authorized_keys
vagrant: generate ssh-config We further split libvm from vagrant. It no longer does 'vagrant ssh-config'. Instead, it always assumes that an ssh-config is provided. We now have complete separation of libvm from vagrant. We change the ansible provisioner as follows: - Allow passing in a VAGRANT_BOX env var to override the default CentOS box. - No longer assume that the root user account is unlocked and has a valid 'vagrant' password. This worked for the centos box but isn't sure to work on every box. Instead, we now just run ansible as the default vagrant user, and during provisioning set up the root account and generate an ssh-config so that libvm can connect directly as root. - No longer build the buildimg during provisioning. This actually stopped working a while ago since the default rsync is disabled. We can just let the buildimg get created on the first compilation. In practice, the bigger issue isn't creating the buildimg, but being able to easily update the host and buildimg pkgs. Closes: #516 Approved by: jlebon
2016-10-31 23:26:56 +03:00
# make sure root account is unlocked
- name: unlock root account
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
shell:
cmd: 'passwd -u root && touch /root/.unlocked'
creates: /root/.unlocked
tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon
2016-06-04 17:48:06 +03:00
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
- copy:
dest: /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
content: |
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.11 (GNU/Linux)
setup.yml: cache buildimg container By far the longest step in provisioning a new VM is the building of the container. This helps alleviate things a little by caching it on the host. It's not a complete solution however. We also need to make it easy to update an existing container. Closes: #344 Approved by: cgwalters
2016-06-22 19:00:45 +03:00
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
mQINBFKuaIQBEAC1UphXwMqCAarPUH/ZsOFslabeTVO2pDk5YnO96f+rgZB7xArB
OSeQk7B90iqSJ85/c72OAn4OXYvT63gfCeXpJs5M7emXkPsNQWWSju99lW+AqSNm
jYWhmRlLRGl0OO7gIwj776dIXvcMNFlzSPj00N2xAqjMbjlnV2n2abAE5gq6VpqP
vFXVyfrVa/ualogDVmf6h2t4Rdpifq8qTHsHFU3xpCz+T6/dGWKGQ42ZQfTaLnDM
jToAsmY0AyevkIbX6iZVtzGvanYpPcWW4X0RDPcpqfFNZk643xI4lsZ+Y2Er9Yu5
S/8x0ly+tmmIokaE0wwbdUu740YTZjCesroYWiRg5zuQ2xfKxJoV5E+Eh+tYwGDJ
n6HfWhRgnudRRwvuJ45ztYVtKulKw8QQpd2STWrcQQDJaRWmnMooX/PATTjCBExB
9dkz38Druvk7IkHMtsIqlkAOQMdsX1d3Tov6BE2XDjIG0zFxLduJGbVwc/6rIc95
T055j36Ez0HrjxdpTGOOHxRqMK5m9flFbaxxtDnS7w77WqzW7HjFrD0VeTx2vnjj
GqchHEQpfDpFOzb8LTFhgYidyRNUflQY35WLOzLNV+pV3eQ3Jg11UFwelSNLqfQf
uFRGc+zcwkNjHh5yPvm9odR1BIfqJ6sKGPGbtPNXo7ERMRypWyRz0zi0twARAQAB
tChGZWRvcmEgRVBFTCAoNykgPGVwZWxAZmVkb3JhcHJvamVjdC5vcmc+iQI4BBMB
AgAiBQJSrmiEAhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRBqL66iNSxk
5cfGD/4spqpsTjtDM7qpytKLHKruZtvuWiqt5RfvT9ww9GUUFMZ4ZZGX4nUXg49q
ixDLayWR8ddG/s5kyOi3C0uX/6inzaYyRg+Bh70brqKUK14F1BrrPi29eaKfG+Gu
MFtXdBG2a7OtPmw3yuKmq9Epv6B0mP6E5KSdvSRSqJWtGcA6wRS/wDzXJENHp5re
9Ism3CYydpy0GLRA5wo4fPB5uLdUhLEUDvh2KK//fMjja3o0L+SNz8N0aDZyn5Ax
CU9RB3EHcTecFgoy5umRj99BZrebR1NO+4gBrivIfdvD4fJNfNBHXwhSH9ACGCNv
HnXVjHQF9iHWApKkRIeh8Fr2n5dtfJEF7SEX8GbX7FbsWo29kXMrVgNqHNyDnfAB
VoPubgQdtJZJkVZAkaHrMu8AytwT62Q4eNqmJI1aWbZQNI5jWYqc6RKuCK6/F99q
thFT9gJO17+yRuL6Uv2/vgzVR1RGdwVLKwlUjGPAjYflpCQwWMAASxiv9uPyYPHc
ErSrbRG0wjIfAR3vus1OSOx3xZHZpXFfmQTsDP7zVROLzV98R3JwFAxJ4/xqeON4
vCPFU6OsT3lWQ8w7il5ohY95wmujfr6lk89kEzJdOTzcn7DBbUru33CQMGKZ3Evt
RjsC7FDbL017qxS+ZVA/HGkyfiu4cpgV8VUnbql5eAZ+1Ll6Dw==
=hdPa
-----END PGP PUBLIC KEY BLOCK-----
- name: Add repository
yum_repository:
name: epel
description: EPEL YUM repo
mirrorlist: 'https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch'
gpgcheck: yes
gpgkey: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
- command: rpm -q fuse-sshfs
register: rpmq_fuse_sshfs
changed_when: False
failed_when: False
vmcheck: adapt for non-vagrant hosts This is just the final bit required to make sure the vagrant and non-vagrant paths can work happily together. It's mostly minor fixes, though the most major change which also affects vagrant is that we now sync to the root home dir, rather than ~vagrant. Closes: #524 Approved by: cgwalters
2016-11-22 06:22:51 +03:00
Redo `vmcheck` to abstract over ssh-config, drop all building My development environment is now using "pet" docker containers. I use VMs for testing things that require that (like rpm-ostree). This patch builds on work from @jlebon in https://github.com/projectatomic/rpm-ostree/pull/509 to rework `vmcheck` such that it can work on any `ssh-config`. By default we expect this to be Vagrant. However, I go a lot farther and delete the `vmbuild` code that was trying to do builds in a container on the target VM. I think this is still worth pursuing at some point, but for now I think it's reasonable to assume that the rpm-ostree developer audience uses Linux as their host workstation and hence has containers. (There's another important point here in that for developing lower level things like rpm-ostree, there's a strong push to make the VM disposable and not a pet) Closes: #516 Approved by: jlebon
2016-11-14 20:07:43 +03:00
- command: rpm-ostree install fuse-sshfs
when: rpmq_fuse_sshfs.rc != 0
Reference in New Issue Copy Permalink