[haiku-development] Re: Haiku buildmasters, now easy

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 22 Feb 2017 08:08:56 -0600

On 2017-02-22 05:06, Ingo Weinhold wrote:

On 22.02.2017 05:55, kallisti5 wrote:
On 2017-02-21 10:27, Axel Dörfler wrote:
Am 21/02/2017 um 15:05 schrieb kallisti5:
Not sure how often I said this already, but please use vmweb for this.
I sent out an email on the progress of the vmweb decom + cleanup to
haiku-sysadmin and haiku-web.

It's been mentioned that vmweb is on it's last legs multiple times by
multiple people.

What does that even mean? It's a VM, and it doesn't serve any real
purpose now anymore, what's the big deal?

it's a vm.  I'm down for reinstalling it as a buildmaster... that was
always one
of the options.   Just concerning when we're asked to use vmweb as-is.
We're not
sure it will upgrade properly at this point :-)

Out of curiosity, if you've dockerized buildmaster, why use a VM at
all instead of running the container directly on baron?

We could.  I was trying to stay within the model baron was originally
configured with (libvirt vm's doing the lifting)

There is a minor blocker to this though:

* Old OpenSUSE on baron. Not sure of the docker version on OpenSUSE 13.1.
Baron's network configuration is complex (Dual zone firewall (DMZ + Public))

waddlesplash did a test upgrade on vmweb to 13.1 to 13.2 yesterday and
the network interfaces changed to the new naming convention which broke
network connectivity. Pair that with potential design firewall changes
    between 13.1 and 42.2 and things are... risky.


So, if we can sort out the OpenSUSE upgrade through 42.2 then this should
be possible... the baron upgrade is going to be messy + scary though.

 -- Alex


Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 02-2017