Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2502)

Unified Diff: README

Issue 7401043: Refactor guts of cmd/juju/get/Run to statecmd.
Patch Set: Refactor guts of cmd/juju/get/Run to statecmd. Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « CONTRIBUTING ('k') | [revision details] » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: README
=== modified file 'README'
--- README 2013-01-09 11:11:45 +0000
+++ README 2013-02-21 14:09:17 +0000
@@ -65,6 +65,11 @@
Change the Ubuntu series name and architecture to match your system.
+Note that the use of --upload-tools forces the instances to run with the same
+series and architecture of your development system. Currently the only
+supported architecture that can be deployed is amd64, so you must develop on
+64-bit machines.
+
Getting juju-core
=================
@@ -118,3 +123,15 @@
bootstrap process.
juju bootstrap -e your-environment --upload-tools {--debug}
+
+Known issues
+============
+
+* If you have used the Python version of Juju, you cannot re-use the
+ control-bucket on S3 for Go Juju. Change the bucket name in your
+ environments.yaml.
+
+* juju-origin is not supported so it must be removed from the environment you
+ define in environments.yaml if it exists. At the moment --upload-tools is
+ the work-around to use, though it does have the problems mentioned
+ previously.
« no previous file with comments | « CONTRIBUTING ('k') | [revision details] » ('j') | no next file with comments »

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b