Build virtual machines (Amazon EC2 ami images for 0.3.20)

TwistedPair

newbie

Activity: 17

Merit: 0

Quote from: Gavin Andresen on September 06, 2011, 09:44:19 PM

0.3.24 Linux/Windows releases weren't built on EC2, but was built on 'gitian' virtual machines (lookup trusted build process here for more info, or get in touch with devrandom).

Thanks for your response.

The reason I asked about EC2 is because I couldn't find step-by-step tutorial to build using Gitian (under Win or Linux). Seems like a great idea, but it appears the building steps are spread out across many posts/readmes/webpages so I'm struggling to make sense of it all.

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

0.3.24 Linux/Windows releases weren't built on EC2, but was built on 'gitian' virtual machines (lookup trusted build process here for more info, or get in touch with devrandom).

TwistedPair

newbie

Activity: 17

Merit: 0

Quote from: TwistedPair on September 05, 2011, 09:25:21 PM

Are there new EC2 AMI for the latest bitcoin builds?

Anyone? Thanks Wink

TwistedPair

newbie

Activity: 17

Merit: 0

Are there new EC2 AMI for the latest bitcoin builds?

Current-C

full member

Activity: 124

Merit: 100

I was able to run the windows vm (thanks Gavin!) but I'd like to access a linux vm (I'm using Win 7). I downloaded Penguinet to try and connect with the ssh keypair but I really have no idea what I'm doing. Can you be more specific about the following:

Quote

After launching the Linux VMs, you login as root (using the ssh keypair you specify when you launch).

How do I connect to a Linux vm with my Win 7 machine?

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

Quote from: Current-C on April 18, 2011, 02:59:14 PM

Ok I tried accessing windows AMI with remote desktop using the ip address(?) as the name of the remote computer (after starting the instance in Amazon) and it wouldn't connect. Can someone help a non-techie figure out what I'm doing wrong?

When you launch your instance, make sure the firewall ("Security Group" in AWS-speak) is setup to allow remote desktop access from your machine's IP address to port 3389.

I run Remote Desktop Client on my Mac, but the process should be the same on PC.

Connect using the "Public DNS" machine name-- something like: ec2-184-2-91-236.compute-1.amazonaws.com

Login as Administrator, password: bitcoin development

(I just launched the 0.3.20.2 Windows AMI to get ready to build a 0.3.21 release candidate).

Current-C

full member

Activity: 124

Merit: 100

Ok I tried accessing windows AMI with remote desktop using the ip address(?) as the name of the remote computer (after starting the instance in Amazon) and it wouldn't connect. Can someone help a non-techie figure out what I'm doing wrong?

Thanks!

devrandom

newbie

Activity: 26

Merit: 0

Quote from: Gavin Andresen on March 19, 2011, 03:13:37 PM

Quote from: devrandom on March 19, 2011, 02:55:51 PM

Gavin,

Did you get a chance to build using the gitian process? Would be cool to compare hashes.

I didn't-- the first "community build" took long enough as it was, and I didn't want to add one more 'different from the way it was done before' variable.

Next release I want to automate some of the manual steps, and maybe use the gitian process, assuming it will work inside an Amazon VM (DO nested virtual machines work?). Unless anybody feels motivated to step in and do it first; with a verifiable build, anybody can take on the role of build-meister.

VM within VM is tricky and I haven't tried it. Maybe I should add EC2 API support to the gitian tools.

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

Quote from: devrandom on March 19, 2011, 02:55:51 PM

Gavin,

Did you get a chance to build using the gitian process? Would be cool to compare hashes.

I didn't-- the first "community build" took long enough as it was, and I didn't want to add one more 'different from the way it was done before' variable.

Next release I want to automate some of the manual steps, and maybe use the gitian process, assuming it will work inside an Amazon VM (DO nested virtual machines work?). Unless anybody feels motivated to step in and do it first; with a verifiable build, anybody can take on the role of build-meister.

devrandom

newbie

Activity: 26

Merit: 0

Gavin,

Did you get a chance to build using the gitian process? Would be cool to compare hashes.

http://bitcointalk.org/index.php?topic=2926.20

https://github.com/bitcoin/bitcoin/blob/27b7f3b43a3868cd4d4f97e03c35074c2ef12349/contrib/gitian.yml

Gavin Andresen

legendary

Activity: 1652

Merit: 2216

Chief Scientist

I've made public the windows, linux32 and linux64 Amazon Machine Images used to build bitcoin 0.3.20. If you have an Amazon EC2 account, you can launch them and have your own working build environment for linux or windows bitcoin (paid for by the hour).

They are:
  ami-4adf2c23 32-bit Linux (Ubuntu 9.04)
  ami-12df2c7b 64-bit Linux (Ubuntu 9.04)
  ami-7a21d213 Windows (with MinGW)

All created in the us-east-1b zone (I don't know if Amazon automatically migrates public AMIs across the world).

After launching the Linux VMs, you login as root (using the ssh keypair you specify when you launch).

After launching the Windows VM, you connect via Remote Desktop and then login as Administrator, password "bitcoin development" (you should change that for your instance as soon as you login, of course).

They contain bitcoin, bitcoind, and everything needed to build them, already built. You could launch instances and try to generate coins, but that's not cost-effective.

(Updated 22 Feb with 0.3.20.01 Windows AMI)

Topic: Build virtual machines (Amazon EC2 ami images for 0.3.20) (Read 3328 times)