]
Sent: Thursday, October 02, 2014 4:44 PM
To: Nicholas Chammas
Cc: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
02, 2014 4:44 PM
To: Nicholas Chammas
Cc: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
On a related note, the current AMI
: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
On a related note, the current AMI for hvm systems (e.g. m3.*, r3.*)
has
a bad
: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
On a related note, the current AMI for hvm systems (e.g. m3.*,
r3.*)
has
a bad package for httpd, whcih
Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
On a related note, the current AMI for hvm systems (e.g. m3.*, r3.*) has
a bad package for httpd, whcih causes
...@gmail.com]
Sent: Thursday, October 02, 2014 4:44 PM
To: Nicholas Chammas
Cc: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http://www.packer.io/intro/getting-started/build-image.html
On a related note, the current AMI for hvm systems (e.g. m3.*, r3.*) has
a bad package
Nate
-Original Message-
From: David Rowe [mailto:davidr...@gmail.com]
Sent: Thursday, October 02, 2014 4:44 PM
To: Nicholas Chammas
Cc: dev; Shivaram Venkataraman
Subject: Re: EC2 clusters ready in launch time + 30 seconds
I think this is exactly what packer is for. See e.g.
http
It should be possible to improve cluster launch time if we are careful
about what commands we run during setup. One way to do this would be to
walk down the list of things we do for cluster initialization and see if
there is anything we can do make things faster. Unfortunately this might be
pretty
On Thu, Jul 10, 2014 at 8:10 PM, Nate D'Amico n...@reactor8.com wrote:
Starting to work through some automation/config stuff for spark stack on
EC2 with a project, will be focusing the work through the apache bigtop
effort to start, can then share with spark community directly as things
You are partially correct.
It's not terribly complex, but also not easy to accomplish. Sounds like you
want to manage some partially/fully baked AMI's with the core spark libs and
dependencies already on the image. Main issues that crop up are:
1) image sprawl, as libs/config/defaults/etc
11 matches
Mail list logo
