ReleaseEngineering/Platforms/Android: Difference between revisions

Line 124: Line 124:
* Select the AMI and launch an instance
* Select the AMI and launch an instance
* Choose m3.medium
* Choose m3.medium
* Select "Review and Launch"
* Click "Next: Configure Instance Details" instead of "Review and Launch"
* Change "Network" to "vpc-b42100df"
** chose a build or try subnet (I think)
* Click "Launch"
* Click "Launch"
** As key pairs select "Choose an existing key pair" and "aws-releng"
** As key pairs select "Choose an existing key pair" and "aws-releng"
* Find the instance and name it so you can find it later
* Find the instance and name it so you can find it later
* Once running, load the aws-releng key on cruncher: [[ReleaseEngineering/How_To/Loan_a_Slave#Environment_Setup|setup environment]]
* Once running, load the aws-releng key on cruncher: [[ReleaseEngineering/How_To/Loan_a_Slave#Environment_Setup|setup environment]]
* You can then ssh into the machine using the private ip e.g:
ssh ubuntu@10.134.54.50
sudo su -
passwd ubuntu # so you can change the password and loand it
* [https://bugzilla.mozilla.org/enter_bug.cgi?bug_severity=major&short_desc=please%20give%20FULL_LDAP_ADDRESS%20access%20to%20FQDN_OF_SLAVE&component=Infrastructure%3A%20OpenVPN&product=Infrastructure%20%26%20Operations&cc=:REQUESTING_USER&comment=FIRST_NAME_REQUESTING_USER%20needs%20access%20to%20FQDN.%0APlease%20grant%20the%20host%20and%20user%20vpn_releng_loan File an IT bug to get the developer access to the slave], and mark it as '''blocking''' the developer request bug.


== Deployment of artifacts ==
== Deployment of artifacts ==
Confirmed users
3,990

edits