Commit Graph

280 Commits (c16ff84e925ea56a8753bb0cd2650c8e9a71ff1c)

Author SHA1 Message Date
Matt Bruzek cdc671a86f Setting the default release number to v0.15.0 2015-04-22 16:39:36 -05:00
Matt Bruzek b69792535d Updating guestbook with the v1beta3 json files. 2015-04-22 15:05:46 -05:00
Matt Bruzek b4766bb380 Removing unneeded status check before juju deployer 2015-04-22 14:45:50 -05:00
Matt Bruzek 450f1f0215 Using readlink instead of realpath. 2015-04-22 12:53:30 -05:00
Matt Bruzek dbca4bf5dd Using python to parse the json output from Juju. 2015-04-22 11:36:37 -05:00
Matt Bruzek 5deef09178 Exporting master and minion variables and calling detect methods in kube-up. 2015-04-22 11:35:49 -05:00
Matt Bruzek 35301bbcfd Merge branch 'add-charms' of github.com:mbruzek/kubernetes into add-charms
Resolved conflicts in:
	cluster/juju/util.sh
2015-04-22 10:36:42 -05:00
Matt Bruzek af15d6d614 Removed the need for an extra python file. i
- Formatted for consistency
- Used different variables for juju directory
2015-04-22 10:31:26 -05:00
Matt Bruzek 3342bb42e0 Removed extra c in path to distro files. 2015-04-22 10:29:55 -05:00
Matt Bruzek 5f59e167fd Editing the local bundle to use github. 2015-04-22 10:29:07 -05:00
Whit Morriss 0ab77ae8be line formatting 2015-04-22 09:40:47 -05:00
Whit Morriss a57a64781a scripting tweaks
- use absolute path for kube_root (fixes JUJU_REPOSITORY directory creation issue) - shortcircuit status polling (for rerunning kubeup)
 - more granular polling iterations
2015-04-22 09:40:47 -05:00
Whit Morriss cc81044230 use git copy of docker charms for debugging 2015-04-22 09:40:47 -05:00
Matt Bruzek 9d21292646 Changing bundle to v0.15.0 and docker git head. 2015-04-21 16:50:47 -05:00
Matt Bruzek 60e0a77a0c Removing cadvisor and normalizing python quotes. 2015-04-21 16:46:21 -05:00
Matt Bruzek c1a56187b8 Removing debug statements from the python code. 2015-04-21 11:02:47 -05:00
Matt Bruzek 85e0e9d6c7 Adding a slash to continue the line. 2015-04-21 11:02:02 -05:00
Matt Bruzek f201379938 Merge pull request #1 from whitmo/new-cadvisor-port
Change cadvisor port and point kubelet to find it
2015-04-20 17:17:18 -05:00
Whit Morriss 7b3534e012 move cadvisor port to 4193 to avoid collision with kubelet 2015-04-20 17:07:19 -05:00
Matt Bruzek a5da3708d2 Removing old docs, setting latest false on docker 2015-04-20 17:00:41 -05:00
Matt Bruzek 7802db4862 Added protetecion if the arguments are not there. 2015-04-20 16:57:42 -05:00
Matt Bruzek 3dd62a5c65 Log the JSON output from BASH 2015-04-20 16:55:08 -05:00
Matt Bruzek 57683ce0ec Adding deployer to the dependency list. 2015-04-17 17:25:23 -05:00
Matt Bruzek 89043414f6 Changed the kube-up logic to use local bundles and charms.
Implemented a feature of kube-down
Corrected a bug on bootstrap of Juju environment.
2015-04-17 17:23:53 -05:00
Matt Bruzek 8f038a82a4 Adding a python file to parse the IP addresses. 2015-04-17 17:22:48 -05:00
Matt Bruzek af8f31a0cd Adding the Juju charms to the cluster directory. 2015-04-17 17:21:37 -05:00
Matt Bruzek 4ff2e53fee Adding the initial Juju bundle to the cluster 2015-04-17 17:20:07 -05:00
Charles Butler a68de6237b Rewrote shell script headers with accepted kubernetes boilerplate
because of failing build notifications on #5414
2015-03-26 16:35:24 -04:00
Charles Butler 5acce1b245 Implement the feedback from filbranden
- Changed check_for_ppa to be parameterized
- Added bash strictmode
- refactored the package_status method to consume variables and be a bit
  nicer to future re-use of the method.
- Cut out extra echo -n statements in favor of tr -d or native awk
- Refactored branching logic paths to leverage double brackets
- normalized local variable annotation
- Updated globals to be all CAPS
- remainder of filbrandens feedback in validate-cluster.sh
2015-03-16 18:35:33 -04:00
Charles Butler ea0978f4f2 Adds JUJU to the Kubernetes Provider listing
This feature adds Juju provisioning to the kube-up script. It currently
parses out the pre-requisits on debian/ubuntu based systems and installs
them if they are missing.

From there we followed the integration path that was found in the
libvirt-coreos path, implementing the methods found in the boilerplate
and calling juju service calls. There are a few "arbitrary sleeps" in
the code to allow the cloud provider to settle and properly deploy.
These are work-around cases from the script executing faster than juju
was able to communicate from the state server to subsequent nodes. I
left comments inline at these points.

To exercise this:

    export KUBERNETES_PROVIDER=juju
    cluster/kube-up.sh

It will spin up a ref arch with 1 Kubernetes Master, 2 minions, and run
the cluster validation checks against the deployment. Bridging the gap
between the juju specific bits and the upstream recommended guides for
getting started with Juju.

To note, if you do not have a "current environment" set in Juju, it will
spin up the quickstart integration wizard in interactive mode, allowing
you to configure juju, and add the proper provider/use it. Otherwise it
assumes you're in the provider you wish to use, and will deploy there.
2015-03-12 19:34:03 -04:00