search

riptano / ComboAMI

The AMI takes a set of input parameters via the EC2 user-data to install, RAID, ring, and launch a DataStax Enterprise/Community cluster.
69 stars 59 forks source link

change gpg calls to use port 80 #31

Closed ablundgren closed 10 years ago

ablundgren commented 10 years ago

This change reduces the number of outbound ports that must be opened in a locked down env.

joaquincasares commented 10 years ago

Great, thanks. I'll test this and merge this on Monday.

joaquincasares commented 10 years ago

I've pushed the change and tested it. Thanks again!

joaquincasares commented 10 years ago

Hello @ablundgren ,

I just wanted to let you know that I reverted this commit. For now, can you instead use port 389 on any 2.4 AMI launches? This is due to a high failure rate that is associated with this protocol.

I'll be adding the keys to the github repo for the 2.5 AMIs so it shouldn't require this port at all any more. I'll update you here when we release these new AMIs. If you need early access, email me your AWS account number and I can hopefully get you these new AMI ids tonight.

Cheers.

ablundgren commented 10 years ago

One path I am considering is adding a pre script that will allow us to specify our own repos, in addition to install java. I have added a flag that causes it not to install JAVA already, and will probably do the same for the add-repos section of the script.

This allows us to install from a controlled source and also eliminates the need for the gpg server. (For some reason today we couldn't get to the debian.datastax.com site and were unable to install, that would eliminate that issue for us as well.)

joaquincasares commented 10 years ago

I'm not sure what you're referring to exactly, but let me know if you need any help with that.

Also, you may want to take a look at our new 2.5 branch, which the new AMIs will be based off of. They already come with Java7 installed. Also, swapping out repos will be an easy fix as long as you provide a flag for that. I would be happy to commit a repo-swap pull request.

I just realized that we still rely on pulling down the repo key for apt-get. I'll ensure I patch that up as well with a local copy of the repo key.

ablundgren commented 10 years ago

When are the new AMI's going to be built?

Is JAVA 7 still being downloaded via the package that does a website scrape?

joaquincasares commented 10 years ago

I did a full baking session last Friday, but missed out one piece that's going to cause another full bake. Hopefully by the end of today.

Oh and Java7 will be preinstalled using these commands: https://github.com/riptano/ComboAMI/blob/2.5/presetup/pre_1.sh#L31

ablundgren commented 10 years ago

That is one less change that I would have needed.

It looks like we have taken a different direction now though and will be headed down building our own AMI. I would still like to contribute a cloudformation template that can deploy into a vpc. Have you come up with where you would like that added?

joaquincasares commented 10 years ago

Nice. Let me know if you ever make changes to infrastructure or settings that you find work better. It'd be great to keep this contributed back to the community through the AMI. :)

Yes, let's create a "community_cloud" folder on the top-level?

Also, you mentioned that this script added nodes in multiple-dc's. Could you attach sample outputs of nodetool ring and nodetool status of these launches when you create the pull request? Thanks!