Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature cloud config file #2

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

mishak87
Copy link
Contributor

Extended cloud-config.yaml file with some common and sane settings.

Added support for private network.
If private network is available it is used for etcd peer address unless CROSS_CLOUD=1 is set.

Basic settings for fleet:
HOSTNAME=coreos01
METADATA="disk=ssd,provider=digital-ocean"
and etcd:
DISCOVERY=https://discovery.etcd.io/<token>

EDIT: Replaced ip variables with actual values.

@ibuildthecloud
Copy link
Owner

Based on your previous issue (and the fact I was just stuck in an airport for 3 hours). I rewrote this script so that it 1) uses less memory 2) can be ran as one line, not the two step process today 3) custom cloud config support and 4) support configuring private networking. I'll review this pr and see of your changes are still applicable

@mishak87
Copy link
Contributor Author

Both pulls are extending cloud-config.yaml (tested properly on 1GB and 512MB ubuntu 14.04 and debian 7.0 x64). It worked on 512MB today so I am happy.

@ibuildthecloud
Copy link
Owner

I just pushed the rewritten script at https://github.com/ibuildthecloud/coreos-on-do/tree/automation I haven't fully tested it yet and will over the weekend. I'll test all the regions too. The main motivation for why I rewrote it was that I really wanted to be able to automated the deployment of CoreOS on DO. The approach I was taking before was forcing you to log into the DO web console. So I took a completely different (and more complicated) approach. But now you can fully automate the deployment of nodes. You can look at the README.md on how to do that. But again, I haven't fully tested it.

@mishak87
Copy link
Contributor Author

If you will need help with testing ping me.

@geekgonecrazy
Copy link

Good deal will test this.

@ibuildthecloud
Copy link
Owner

@aaronogle @mishak87 I just merged the automation branch to master. If you have time it would be nice if you could test it out. I personally tested 512mb droplets in all open regions.

@mishak87
Copy link
Contributor Author

Well with their API and your fully automated script testing gets significantly easier :) Could you share your testing script?

@geekgonecrazy
Copy link

@ibuildthecloud Deployed 2 so far, works like a dream. Deployed with a very basic cloud config, will try some more advanced soon. But looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants