HACKING.md: clarify details about the spawned VM

Also add a comment to tools/deploy/test/user-data explaining where the
IP comes from.
This commit is contained in:
Lars Karlitski 2020-10-07 18:31:50 +02:00
parent 6a1b9f17ce
commit e87d3bd3e1
2 changed files with 12 additions and 2 deletions

View file

@ -28,8 +28,14 @@ mimick what is run on *osbuild-composer*'s continuous integration
infrastructure, i.e., installing `osbuild-composer-tests` and starting the
service.
You can log into the running machine as user `admin`, with the
password `foobar`. Stopping the machine loses all data.
The virtual machine uses qemu's user mode networking [1], forwarding port 22 to
the host's 2222 and 443 to 4430. You can log into the running machine with
ssh admin@localhost -p 2222
The password is `foobar`. Stopping the machine loses all data.
For a quick compile and debug cycle, we recommend iterating code using thorough
unit tests before going through the full workflow described above.
[1]: https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29

View file

@ -1,5 +1,9 @@
#cloud-config
yum_repos:
# Fetch osbuild packages from a repository served on the host.
#
# In qemu user networking, 10.0.2.2 always points to the host:
# https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29
osbuild:
name: osbuild
baseurl: "http://10.0.2.2:8000"