From owner-freebsd-virtualization@FreeBSD.ORG Wed Jun 25 20:28:58 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DF0C1BF; Wed, 25 Jun 2014 20:28:58 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC2F621F6; Wed, 25 Jun 2014 20:28:57 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id z11so2202503lbi.24 for ; Wed, 25 Jun 2014 13:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=rS4wLdAEbX0sqKrBcA1PP94EvjOwzs83cJ4nw6KHtJk=; b=wa0LYJCoCKHKsbKYh4Q+QbBDMUZ4VhHGR0olvLl5wCMbSSrb6qgwWtUffmg+mu5woZ b3f/4DIs35mU5PhI59/87db9jC/ndlvPGf2qEOmW8IXOi1e/W8hqe036Qqeb9y/YhwQV lVDT7J2d30YBJuvgHXUyGVpRzlly57dMVX9QPSup/gakLCKl/uCZIcgBSDWKPCBE9CW5 ub4etA0aFywC8Q6diike2UbR6TSKE6GfRSdyQbd4nsVbkP8W5EWrKYpKK43rF1nsqoeO 1MTO6BnSbxhrmXQDAOrAWTZXUtCYT1B+eOe6hf9rIep0L5KlP+GU40QtDBs3s9unJ+KK 9dXA== MIME-Version: 1.0 X-Received: by 10.152.28.194 with SMTP id d2mr7492228lah.25.1403728135680; Wed, 25 Jun 2014 13:28:55 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.67.71 with HTTP; Wed, 25 Jun 2014 13:28:55 -0700 (PDT) In-Reply-To: <20140625180810.GB1304@kloomba> References: <20140621135159.GA47374@kloomba> <20140625180810.GB1304@kloomba> Date: Wed, 25 Jun 2014 13:28:55 -0700 X-Google-Sender-Auth: 3Mzmy8xSw0-xL3ccKsEcp4wS2Q0 Message-ID: Subject: Re: libvirt, bhyve, and Jenkins configuration problems From: Craig Rodrigues To: Roman Bogorodskiy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2014 20:28:58 -0000 On Wed, Jun 25, 2014 at 11:08 AM, Roman Bogorodskiy wrote: > > Does that mean that I need to configure my VM, so that it comes up with a > > known IP, so that > > it can be entered on this configuration page? > > Correct. > > Though, normally you don't need to perform any special configuration for > the IP address as long as the networking configuration is correct. > > The VM just needs to be configured to obtain an IP address via DHCP. > Later on it should be persistent in dnsmasq. > > An IP address could be obtained either from the dnsmasq leases file or > from arp cache for example. > But how does the Jenkins libvirt plugin know the IP address for the VM, unless you enter it in this field in the Jenkins UI? > > > Also, the VM, that is spawned, it must have openjdk installed? Does that > > mean that > > after libvirt starts the VM, Jenkins will try to SSH into the VM and > start > > a Jenkins job > > by invoking java? > > Yes, it's true, it starts its agent which does the job. > > PS Maybe there are other ways to push Jobs to Jenkins nodes, but I > didn't look close into that. > The easiest way is to have the openjdk installed in the VM, so that Jenkins can ssh in and run jobs. However, there is also the Publish Over SSH Plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin ) which allows Jenkins to SSH into a remote host and run different commands, instead of starting a full Jenkins job, which requires the openjdk to be available. -- Craig