Closed Bug 1205957 Opened 9 years ago Closed 8 years ago

[tools] create new loads-broker,v2 / loads-web,v2 instances in cloudservices-aws-stage IAM

Categories

(Cloud Services :: QA: Test Automation, defect)

Product:
Cloud Services
Component:
QA: Test Automation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: rpapa, Assigned: kthiessen)

References

Details

Currently we're running loadsv2 in the old cloudsvc IAM (oregon) so that loads-web could communicate with loadv1-broker and loadsv2-broker. Since the cloudsvc IAM has been deprecated, we should create new instances for both in the moz-svc IAM (default us-east region)
Assignee: sphilp → kthiessen
Status: NEW → ASSIGNED
The instance for loads-web has been created, although loads-web has not yet beein installed on it.

Its Route53 DNS name is loads-web.qa.mozaws.net -- current IP is 54.172.8.13.

Login is ubuntu@loads-web.qa.mozaws.net -- use the loads.pem key.  (We may switch keys later.)
That'll teach me to advertise ahostname before I verify it.

*.qa.mozaws.net don't actually seem to be propagated into the world.  I'll file a separate bug for that.

Meanwhile, new name:  loads-web-v2.stage.mozaws.net

Same IP, same key.
Another instance:  loads-broker-v2.stage.mozaws.net.

Same key (loads.pem), same user (ubuntu).

With any luck, Richard and Tarek and I will install the software later today.
Morphing bug to reflect the fact that moz-svc-dev is now cloudservices-aws-stage.
Summary: [tools] create new loads-broker,v2 / loads-web,v2 instances in moz-svc IAM → [tools] create new loads-broker,v2 / loads-web,v2 instances in cloudservices-aws-stage IAM
Resolving this bug as INCOMPLETE, since the work has moved over to :chartjes with the Loads project.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.