From owner-freebsd-current@freebsd.org Sun Jul 16 20:44:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9F94C79791; Sun, 16 Jul 2017 20:44:13 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from forward19p.cmail.yandex.net (forward19p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::aa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 782626602A; Sun, 16 Jul 2017 20:44:13 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::28]) by forward19p.cmail.yandex.net (Yandex) with ESMTP id 93E34214F2; Sun, 16 Jul 2017 23:44:09 +0300 (MSK) Received: from smtp4o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4o.mail.yandex.net (Yandex) with ESMTP id E14EF6C01102; Sun, 16 Jul 2017 23:44:07 +0300 (MSK) Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id nXe8AUYaT0-i7f0BN88; Sun, 16 Jul 2017 23:44:07 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1500237847; bh=Km3dMH/w/DYrxjQz/ot4T6Ql3JyTlIC8Ch/yLBr5iW8=; h=To:From:Subject:Message-ID:Date; b=HcE/OenXbp2DhALc++rUbhO3D4g/ewxT9SvO2TW8rXYz9HgjzCUhyxYLU75DrwUTA qx/qDDxFpUBd9e8n+0rvwgcq6oUtHh0xB3evAhQTVMn4NE8lG5wbzdX2oQ+HWGUJBL MuGPzTSvjtwhoCPtedWJLW93KeJextSU8Gt3b0BU= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 1022867361,1 0,1 0 To: FreeBSD Current , "freebsd-hackers@freebsd.org" From: Panagiotes Mousikides Subject: Attn: CI/Jenkins people; Run bhyve instance for testing pf Message-ID: <871d6043-0c56-2c9b-1e3e-5db33898c24a@yandex.com> Date: Sun, 16 Jul 2017 20:44:06 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jul 2017 20:44:13 -0000 Hello everybody! I am working on adding tests to the FreeBSD test suite for testing pf, the network packet filter. These tests need at least two machines running and connected to each other, with one machine generating network traffic and the other running pf and filtering the traffic. I am looking for a way to fire off a bhyve instance to serve as the second machine, the first being the actual machine I am running the tests on. This should be done completely automatically, with scripts to configure all network interfaces and to preferably also set up an SSH server on the bhyve instance. This bhyve instance could start off as running the latest stable version of FreeBSD, or it could be configured to run a snapshot of the development tree. The aim is to have the desired version of FreeBSD that we want to test running on it. Ideally this would be done in such a way that we can reuse the machine for further tests, instead of rebuilding everything from scratch for each test. What I am looking for is the best way to do this, preferably so that it can be easily integrated into the CI work being done at Jenkins. What do you think? Any input is welcome! All the best, Panagiotes