This Gist is now part of https://github.com/gmasse/ovh-ipxe-customer-script
| package backends | |
| import ( | |
| "fmt" | |
| "io" | |
| "strings" | |
| "sync" | |
| "time" | |
| "github.com/docker/libswarm" |
| This is based on http://serverascode.com/2014/03/13/boot2docker-qemu.html | |
| After running the script, you should be able to login using: | |
| ssh-keygen -R $IP # if the host-key is already know for that IP-address | |
| ssh-keyscan -p 22 $IP > /var/lib/libvirt/images/boot2docker1.hostfile | |
| ssh-keygen -H -f /var/lib/libvirt/images/boot2docker1.hostfile | |
| rm -f /var/lib/libvirt/images/boot2docker1.hostfile.old | |
| ssh -p 22 -o UserKnownHostsFile=/var/lib/libvirt/images/boot2docker1.hostfile -i /var/lib/libvirt/images/boot2docker1.key docker@$IP |
| heat_template_version: 2013-05-23 | |
| description: Deploy a CoreOS cluster that tracks the Stable Channel | |
| parameters: | |
| count: | |
| description: Number of CoreOS machines to deploy | |
| type: number | |
| default: 3 | |
| constraints: |
| # This is an example of the Stack Exchange Tier 1 HAProxy config | |
| # The only things that have been changed from what we are running are: | |
| # 1. User names have been removed | |
| # 2. All Passwords have been remove | |
| # 3. IPs have been changed to use the example/documentation ranges | |
| # 4. Rate limit numbers have been changed to randome numbers, don't read into them | |
| userlist stats-auth | |
| group admin users $admin_user | |
| user $admin_user insecure-password $some_password |
| root@services1:~# wget http://crosbymichael.com/debian.jessie && chmod +x debian.jessie | |
| --2014-12-11 21:41:15-- http://crosbymichael.com/debian.jessie | |
| Resolving crosbymichael.com (crosbymichael.com)... 54.231.1.100 | |
| Connecting to crosbymichael.com (crosbymichael.com)|54.231.1.100|:80... connected. | |
| HTTP request sent, awaiting response... 200 OK | |
| Length: 84455326 (81M) [binary/octet-stream] | |
| Saving to: ‘debian.jessie’ | |
| 100%[=========================================================================>] 84,455,326 17.9MB/s in 10s |
| #!/usr/bin/env python | |
| import argparse | |
| import os | |
| import prettytable | |
| from novaclient.v1_1 import client as novaclient | |
| OS_USERNAME = os.environ['OS_USERNAME'] | |
| OS_PASSWORD = os.environ['OS_PASSWORD'] |
- Must be an event that someone involved in open source would be interested in attending
- Must be a community oriented event (no corporate owned for-profit events here please)
- Can't be about a specific language/framework.
Leave suggestions in the comments below
I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.
- Two developers working on independent features must never be blocked by each other
- No code freeze! Ever! For any reason!
- A developer must be able to base derivative work on another developer's work, without waiting for any third party
- Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
- Developers must be able to work on multiple features simultaneously, or at lea
The purpose of this document is to make recommendations on how to browse in a privacy and security conscious manner. This information is compiled from a number of sources, which are referenced throughout the document, as well as my own experiences with the described technologies.
I welcome contributions and comments on the information contained. Please see the How to Contribute section for information on contributing your own knowledge.