781955 - Virtual machine for hg testing

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Ben Kero [:bkero]]

A virtual machine is needed for hg testing.  I looked on mana, but couldn't find any sort of template to request one.  The requirements for this are:

Name: hg-test.dmz.scl3.mozilla.com
1 CPU
1GB RAM
20GB hard drive space

1 network interface, same vlan as the other hg servers (vlan74)

Please add access to the same NFS shares as the other hg servers (10.22.74.10, /vol/hg_ecma, /vol/hg_pvt, /vol/hg/hg_qtree)

Comment 1

[Shyam Mani [:fox2mike]]

We should probably call this hg.stage.dmz.scl3.mozilla.com

Comment 2

[Shyam Mani [:fox2mike]]

now that I think of it, hgssh.stage.dmz.scl3 

I should sleep :)

Comment 3

[(not currently active) Ted Mielczarek]

We used to have a hgstage.mozilla.com, I don't know what ever became of it.

Comment 4

[Adrian J Fernandez [:Aj]]

VM is online, added to inventory, puppetized and basic nagios checks added.

By default, VM template comes with 40G disk (enjoy the extra space!).

Waiting on bug 784151 for NFS mounts.

Comment 5

[Adrian J Fernandez [:Aj]]

VM ready to go.

Filesystem            Size  Used Avail Use% Mounted on
10.22.74.10:/vol/hg/hg_qtree
                      300G   62G  239G  21% /repo/hg
10.22.74.10:/vol/hg_ecma
                      8.0G  635M  7.4G   8% /repo/hg_ecma
10.22.74.10:/vol/hg_pvt
                       40G  1.1G   39G   3% /repo/hg_pvt

Comment 6

[hwine]

I can't log in with my normal key.

All releng folks should be able to log into this box.

Comment 7

[Justin Wood (:Callek)]

for clarity:

$ hg clone ssh://hgssh.stage.dmz.scl3.mozilla.com/mozilla-central tmp-mc
remote: ssh: connect to host hgssh.stage.dmz.scl3.mozilla.com port 22: Bad file number
abort: no suitable response from remote hg!

Comment 8

[Ben Kero [:bkero]]

Since the hgssh staging machine is missing some of the custom libraries we're using, the syntax for checking out a repository should be:

hg clone ssh://[e-mail]//repo/hg/mozilla-central tmp-mc

Comment 9

[hwine]

How do we log in to view log files? requirement from bug 781012 comment 12, supposedly addressed by account for hwine in bug 781012 comment 15

Comment 10

[Ben Kero [:bkero]]

Hal,

You should be able to log in with:
ssh [e-mail]

I've manually created an account for you. Anybody else from the team will need their own accounts if they want to log in to view logs.

Comment 11

[hwine]

Yep - works now -- thanks!

Let's get one for Callek as well.

Comment 12

[Ben Kero [:bkero]]

I've created one for Callek as well.

Comment 13

[hwine]

Our understanding is that hgssh is in the process of being upgraded to the latest hg server version.

When that is completed, please let us know:
 - specific server version
 - list of any enabled hg extensions on server

Comment 14

[Ben Kero [:bkero]]

The mercurial version I upgraded to was the latest available, which was 2.5.4.

There are no enabled hg extensions on the server other than the defaults that come enabled in this hg version. There is no hgrc file mentioning any enabled extensions.

Comment 15

[hwine]

The hgweb service does not seem to be running - nothing is listening on port 80:

[[e-mail]3 ~]$ netstat -nlt | grep :80
[[e-mail]3 ~]$ nc -vz localhost 80
nc: connect to localhost port 80 (tcp) failed: Connection refused
nc: connect to localhost port 80 (tcp) failed: Connection refused
[[e-mail]3 ~]$

Comment 16

[hwine]

Ah, looks like requirements in blocked bug didn't get transferred here cleanly. For reference, minimal requirements are in bug 781012 comment #10

Given that the fqdn has 'stage' in it, I actually assumed that the setup was functionally identical to production. (Just newer software version & repo list.) Yeah - "assume" :(

Please list what other functionality is not available on the staging instance, or will operate differently. Including:
 hgweb
 pushlog
 hooks

Thanks!

Comment 17

[Justin Wood (:Callek)]

(In reply to Hal Wine [:hwine] from comment #16)
> Ah, looks like requirements in blocked bug didn't get transferred here
> cleanly. For reference, minimal requirements are in bug 781012 comment #10
> 
...
>
> Please list what other functionality is not available on the staging
> instance, or will operate differently. Including:

needinfo-shyam/bkero

Comment 18

[Shyam Mani [:fox2mike]]

Had a check with Hal, this is what needs to be done from IT :

1) Setup hgweb & ssh pull/commit
2) Local r/w copies of try and m-c on the stage machine 
3) Make sure global hooks are the same
4) Make sure hooks on m-c and try are the same as production
5) hgweb templates should be installed 

Ben will work on this.

Comment 19

[Ben Kero [:bkero]]

I've satisfied all the requirements for the host outlined by Shyam earlier.
hgweb and ssh pull/commit are working
Local RW copies of try and mozilla-central exist
Global hooks are the same
Repo-specific hooks are also the same
The templates will be the same as in production

Comment 20

[Shyam Mani [:fox2mike]]

hwine, Callek - can we make sure this fits what you need ASAP? (so we don't have any more blockers waiting on IT for this). Thanks!

Comment 21

[hwine]

Callek will be on this ASAP this morning.

Comment 22

[Justin Wood (:Callek)]

(In reply to Shyam Mani [:fox2mike] from comment #20)
> hwine, Callek - can we make sure this fits what you need ASAP? (so we don't
> have any more blockers waiting on IT for this). Thanks!

It appears I no longer have ssh-shell access. Though I don't feel I really need it, it would make some tasks `slightly` easier. And would have allowed me to answer the one outstanding Q I have.

Q: What is the expected url for the mercurial repos as Apache sees them

** I tried hgssh.stage.dmz.scl3.mozilla.com/ -- which gives me an apache setup page (thats ok)
** I then tried hgssh.stage.dmz.scl3.mozilla.com/mozilla-central which is not found
** I tried hgssh.stage.dmz.scl3.mozilla.com/mozilla-central/ which is also not found
** I tried hgssh.stage.dmz.scl3.mozilla.com//repos/hg/mozilla-central as mentioned elsewhere on this bug.
** Lastly I tried /try incase it was just m-c messed up.

I don't particularly need it anywhere specific I just need to know where it is.

Lastly for sanity incase you decide to look into getting my ssh shell access back log of what I tried and the error messages:

Justin@ORION /d/Sources/drivertools/comm-merges
$ ssh [e-mail]@hgssh.stage.dmz.scl3.mozilla.com
No interactive shells allowed here!
Connection to hgssh.stage.dmz.scl3.mozilla.com closed.

Justin@ORION /d/Sources/drivertools/comm-merges
$ ssh [e-mail]
Permission denied (publickey).

Justin@ORION /d/Sources/drivertools/comm-merges
$ ssh [e-mail]
Permission denied (publickey).

Justin@ORION /d/Sources/drivertools/comm-merges
$ ssh [e-mail]
Permission denied (publickey).

Justin@ORION /d/Sources/drivertools/comm-merges
$ ssh [e-mail]@hgssh.stage.dmz.scl3.mozilla.com
You do not have a valid mercurial account!
Connection to hgssh.stage.dmz.scl3.mozilla.com closed.

---

needinfo on you two for said answer, once I have at least url-to-find-this stuff I expect we're set. but would want one last mini-check to ascertain that for sure

Comment 23

[Shyam Mani [:fox2mike]]

302 bkero.

Comment 24

[Ben Kero [:bkero]]

The pushing problem was related to some incorrect permissions being set. I've since corrected the problem and no more 'Permission denied' errors should be encountered.

Comment 25

[Ben Kero [:bkero]]

The permission problems have been fixed.

I don't see any outstanding issues on why this should be left open. If anybody feels differently please reopen and comment.