831158 - Create oracle.bugzilla.lan VM

Status: RESOLVED FIXED

(Infrastructure & Operations :: Virtualization, task)

Description

[Teemu Mannermaa (:wicked)]

We used to have a Oracle DB test system that was set up in bug 377526 but it was decided to be killed off in bug 719715 instead of migrated. Can I get a new VM setup with a RHEL 6 (stock kernel is fine) so I can bring this back? This would help both our automated tests and our devs to figure things out. What information you would need to get this installed?

I can install the Oracle DB myself once I have a working OS. (I'm planning to go with a version 11g Release 2 Standard Edition using a free OTN license for development/testing purposes, since surprisingly that's all we need.)

Comment 1

[Laura Thomson :laura]

I'm guessing this is no longer needed.

Comment 2

[Dave Miller [:justdave]]

That would be an incorrect guess.  Bugzilla still supports Oracle as a back end, so we still need to be able to test it.

Comment 3

[Dave Miller [:justdave]]

According to bug 719715 the existing VM was deleted with the intention of rebuilding it from scratch on a newer OS because the existing setup was old.  Obviously it was a low priority because nobody poked this bug after it sat so long, but it still ought to be done.

Comment 4

[Kendall Libby [:fubar] (he/him)]

Then perhaps it should move over to community? dev svcs has nothing to do with oracle.

Comment 5

[Dave Miller [:justdave]]

Probably virtualization.  It basically just needs a run-of-the-mill VM set up with RHEL6 on it.  IT doesn't need to care about Oracle, we'll set that up ourselves. :)

Comment 6

[Dave Miller [:justdave]]

This should be set up on the private Bugzilla Community VLAN, not accessible to the Internet.

Comment 7

[Chris Knowles [:cknowles]]

Run of the mill VM's I can do.

Need some information though.

normally the hostname gives me the vlan, but this one doesn't - can you either give me a more explicit pointer to the vlan, or other hosts that are on that vlan?

Assuming that we have that vlan in the VC already - I'll need the following - I've filled in complete guesses, feel free to correct, sneer-derisively, etc.:
# CPUS: 2??
RAM: 4 GB??
HDD: Standard 40GB??
OS: RHEL6-x86_64

Also, would I be right that this should be puppetized with the standard infrastructure puppet, or do you need something special done?

CJK

Comment 8

[Dave Miller [:justdave]]

Base install of RHEL6 (or CentOS 6 if you prefer? it's a community box), enough to get it talking to the network.  No puppet.

Other stuff on the same VLAN:

Host landfill.bugzilla.lan (192.168.99.1) appears to be up.
Host infra.bugzilla.lan (192.168.99.2) appears to be up.
Host cg-bugs01.bugzilla.lan (192.168.99.25) appears to be up.
Host cg-bugs02.bugzilla.lan (192.168.99.30) appears to be up.
Host cg-bugs03.bugzilla.lan (192.168.99.40) appears to be up.
Host update.bugzilla.lan (192.168.99.130) appears to be up.
Host bots.bugzilla.lan (192.168.99.140) appears to be up.

oracle.bugzilla.lan has address 192.168.99.20
^ this exists in DNS, that would be the machine we're creating (it used to exist, got deleted in favor of rebuilding it from scratch during the colo move a while back, rebuilding it is what we're doing now with this bug.

The old one was 1 CPU, 768 MB RAM, 60 GB disk.  I imagine RHEL/CentOS 6 wants more RAM than that, so maybe 1GB or 2GB RAM?  or 2 CPUs and 4GB RAM if that's what the standard is these days. :)

Comment 9

[Chris Knowles [:cknowles]]

Alright, some research later - we've got a vlan labeled "gc-bugs VLAN23" that corresponds to the 192.168.99.1 interface on landfill.bugzilla.org - is there something that vlan should be named to better match it to requests like this?  (bugzilla.lan pops to my forebrain, but if gcbugs is a better name, I'm OK)

Also, noticed in landfill that the eth0 was public and eth1 was this - would you like the eth1 pattern to continue for this private IP?

Other than that, RHEL6, 2CPU, 4G RAM is fine.  Nice thing about VMs, if you don't use it, it doesn't necessarily go to waste.

Let me know and I can proceed on building this out for you.

CJK

Comment 10

[Dave Miller [:justdave]]

Was it "cg-bugs" perhaps?  Not sure if the "Community Giving" program still exists, but it was originally set up under that program back when CG had its own ESX box (which was trashed in favor of integrating it with the main ESX cluster when we moved).

Comment 11

[Chris Knowles [:cknowles]]

Nope, it's definitely gc-bugs - it's even listed as such on the now deprecated mana vlan page.

either way, shouldn't be a problem, but if you'd like to rename it to something more current that might be more helpful in preventing all these questions.

So, do you want the private interface on eth1 - or do you just not care?

Comment 12

[Dave Miller [:justdave]]

bugzilla.lan would be great as long as it doesn't confuse people into thinking it's something for BMO.

Don't really care about the interface, it'll be the only one it has anyway.

Comment 13

[Dave Miller [:justdave]]

wicked says 100GB of disk if we can have it.

Comment 14

[Chris Knowles [:cknowles]]

all 100G in the / or elsewhere?  (/data?)

Comment 15

[Dave Miller [:justdave]]

All in / is fine.

Comment 16

[Chris Knowles [:cknowles]]

Starting on this.

Comment 17

[Chris Knowles [:cknowles]]

Alright, oracle.bugzilla.lan on the gc-bugs vlan IP address 192.168.99.20 exists and had a 100GB disk, the majority of which is on /

Take a look, let me know what you think.

CJK

Comment 18

[Teemu Mannermaa (:wicked)]

Looks good to me, thanks!