1
=== modified file 'source/faq.rst'
2
--- source/faq.rst	2012-04-04 13:58:46 +0000
3
+++ source/faq.rst	2012-04-07 20:04:17 +0000
4
@@ -35,45 +35,56 @@
5
35
  No, juju uses a plain Ubuntu image. All needed components are installed
35
  No, juju uses a plain Ubuntu image. All needed components are installed
6
36
  at run-time. Then the juju charm is sent to the machine and hooks start
36
  at run-time. Then the juju charm is sent to the machine and hooks start
7
37
  getting executed in response to events. If you need a custom AMI you can
37
  getting executed in response to events. If you need a custom AMI you can
9
38
specify it in the environments.yaml file. 
38
  specify it in the environments.yaml file. 
10
39
39
11
40
Is it possible to deploy multiple services per machine?
40
Is it possible to deploy multiple services per machine?
12
41
41
13
42
  Currently each service unit is deployed to a separate machine that can relate
42
  Currently each service unit is deployed to a separate machine that can relate
17
43
to other services running on different nodes. This was done to get juju into a
43
  to other services running on different nodes. This was done to get juju into a
18
44
working state faster. juju will definitely support multiple services per
44
  working state faster. juju will definitely support multiple services per
19
45
machine in the future
45
  machine in the future
20
46
46
21
47
Is it possible to pass parameters to juju charms?
47
Is it possible to pass parameters to juju charms?
22
48
48
23
49
  Tunables are landing very soon in juju. Once ready you will be able to use
49
  Tunables are landing very soon in juju. Once ready you will be able to use
26
50
"juju set service key=value" and respond to that from within the juju charm.
50
  "juju set service key=value" and respond to that from within the juju charm.
27
51
This will enable dynamic features to be added to charms
51
  This will enable dynamic features to be added to charms
28
52
52
29
53
Does juju only deploy to the Amazon EC2 cloud?
53
Does juju only deploy to the Amazon EC2 cloud?
30
54
54
31
55
  No. juju can deploy to EC2, OpenStack, and bare metal via LXC containers or
32
56
Orchestra. When using LXC you are able to run juju charms on a single local
33
57
machine. This is the recommended method for prototyping charms as it's quicker
34
58
to iterate locally and then deploy on the cloud when you're ready to test.
35
59
Also integration work with the `Orchestra <https://launchpad.net/orchestra>`_
36
60
project is underway to enable deployment to hardware machines.
37
61
55
38
56
  No. juju can deploy to EC2, OpenStack, and bare metal (`MAAS
39
57
  <https://wiki.ubuntu.com/ServerTeam/MAAS/Juju>`_) via LXC containers or
40
58
  Orchestra .
41
59
  When using LXC you are able to run juju charms on a single local machine.
42
60
  This is the recommended method for prototyping charms as it's quicker to
43
61
  iterate locally and then deploy on the cloud when you're ready to test.
44
62
62
45
63
63
46
64
What directory are hooks executed in?
64
What directory are hooks executed in?
47
65
65
48
66
  Hooks are executed in the charm directory (the parent directory to the hook
66
  Hooks are executed in the charm directory (the parent directory to the hook
52
67
directory). This is primarily to encourage putting additional resources that a
67
  directory). This is primarily to encourage putting additional resources that
53
68
hook may use outside of the hooks directory which is the public interface of
68
  a hook may use outside of the hooks directory which is the public interface
54
69
the charm.
69
  of the charm.
55
70
70
56
71
How are charms licensed?
71
How are charms licensed?
57
72
72
58
73
  Charms are effectively data inputs to juju, and are therefore
73
  Charms are effectively data inputs to juju, and are therefore
64
74
licensed/copyrighted by the author as an independent work. You are free to
74
  licensed/copyrighted by the author as an independent work. You are free to
65
75
claim copyright solely for yourself if it's an independent work, and to license
75
  claim copyright solely for yourself if it's an independent work, and to
66
76
it as you see fit. If you as the charm author are performing the work as a
76
  license it as you see fit. If you as the charm author are performing the work
67
77
result of a fiduciary agreement, the terms of such agreement come into play and
77
  as a result of a fiduciary agreement, the terms of such agreement come into
68
78
so the licensing choice is up to the hiring entity.
78
  play and so the licensing choice is up to the hiring entity.
69
79
70
80
How can I choose between environments?
71
81
72
82
  You can have as many environments as you want in ``environments.yaml`` and
73
83
  set one as the default either by specifying
74
84
75
85
    ``default: default-env-name``
76
86
77
87
  or via a ``JUJU_ENV`` environment variable. Last but not least the ``juju``
78
88
  subcommands accept an ``-e`` parameter that can be used to specify the name
79
89
  of the desired environment.
80
79
90
81
80
How can I contact the juju team?
91
How can I contact the juju team?
82
81
92
Status:	Merged
Approved by:	Kapil Thangavelu on 2012-04-07
Approved revision:	11
Merge reported by:	Mark Mims
Merged at revision:	not available
Proposed branch:	lp:~al-maisan/pyjuju/env-faq
Merge into:	lp:~juju/pyjuju/docs
Diff against target:	79 lines (+31/-20) 1 file modified source/faq.rst (+31/-20)
To merge this branch:	bzr merge lp:~al-maisan/pyjuju/env-faq
Related bugs:	Link a bug report
Reviewer	Review Type	Date Requested	Status
Kapil Thangavelu (community)		2012-04-07	Approve on 2012-04-07
Review via email: mp+101178@code.launchpad.net
1	=== modified file 'source/faq.rst'
2	--- source/faq.rst 2012-04-04 13:58:46 +0000
3	+++ source/faq.rst 2012-04-07 20:04:17 +0000
4	@@ -35,45 +35,56 @@
5	35	No, juju uses a plain Ubuntu image. All needed components are installed	35	No, juju uses a plain Ubuntu image. All needed components are installed
6	36	at run-time. Then the juju charm is sent to the machine and hooks start	36	at run-time. Then the juju charm is sent to the machine and hooks start
7	37	getting executed in response to events. If you need a custom AMI you can	37	getting executed in response to events. If you need a custom AMI you can
9	38	specify it in the environments.yaml file.	38	specify it in the environments.yaml file.
10	39		39
11	40	Is it possible to deploy multiple services per machine?	40	Is it possible to deploy multiple services per machine?
12	41		41
13	42	Currently each service unit is deployed to a separate machine that can relate	42	Currently each service unit is deployed to a separate machine that can relate
17	43	to other services running on different nodes. This was done to get juju into a	43	to other services running on different nodes. This was done to get juju into a
18	44	working state faster. juju will definitely support multiple services per	44	working state faster. juju will definitely support multiple services per
19	45	machine in the future	45	machine in the future
20	46		46
21	47	Is it possible to pass parameters to juju charms?	47	Is it possible to pass parameters to juju charms?
22	48		48
23	49	Tunables are landing very soon in juju. Once ready you will be able to use	49	Tunables are landing very soon in juju. Once ready you will be able to use
26	50	"juju set service key=value" and respond to that from within the juju charm.	50	"juju set service key=value" and respond to that from within the juju charm.
27	51	This will enable dynamic features to be added to charms	51	This will enable dynamic features to be added to charms
28	52		52
29	53	Does juju only deploy to the Amazon EC2 cloud?	53	Does juju only deploy to the Amazon EC2 cloud?
30	54		54
31	55	No. juju can deploy to EC2, OpenStack, and bare metal via LXC containers or
32	56	Orchestra. When using LXC you are able to run juju charms on a single local
33	57	machine. This is the recommended method for prototyping charms as it's quicker
34	58	to iterate locally and then deploy on the cloud when you're ready to test.
35	59	Also integration work with the `Orchestra <https://launchpad.net/orchestra>`_
36	60	project is underway to enable deployment to hardware machines.
37	61		55
38			56	No. juju can deploy to EC2, OpenStack, and bare metal (`MAAS
39			57	<https://wiki.ubuntu.com/ServerTeam/MAAS/Juju>`_) via LXC containers or
40			58	Orchestra .
41			59	When using LXC you are able to run juju charms on a single local machine.
42			60	This is the recommended method for prototyping charms as it's quicker to
43			61	iterate locally and then deploy on the cloud when you're ready to test.
44	62		62
45	63		63
46	64	What directory are hooks executed in?	64	What directory are hooks executed in?
47	65		65
48	66	Hooks are executed in the charm directory (the parent directory to the hook	66	Hooks are executed in the charm directory (the parent directory to the hook
52	67	directory). This is primarily to encourage putting additional resources that a	67	directory). This is primarily to encourage putting additional resources that
53	68	hook may use outside of the hooks directory which is the public interface of	68	a hook may use outside of the hooks directory which is the public interface
54	69	the charm.	69	of the charm.
55	70		70
56	71	How are charms licensed?	71	How are charms licensed?
57	72		72
58	73	Charms are effectively data inputs to juju, and are therefore	73	Charms are effectively data inputs to juju, and are therefore
64	74	licensed/copyrighted by the author as an independent work. You are free to	74	licensed/copyrighted by the author as an independent work. You are free to
65	75	claim copyright solely for yourself if it's an independent work, and to license	75	claim copyright solely for yourself if it's an independent work, and to
66	76	it as you see fit. If you as the charm author are performing the work as a	76	license it as you see fit. If you as the charm author are performing the work
67	77	result of a fiduciary agreement, the terms of such agreement come into play and	77	as a result of a fiduciary agreement, the terms of such agreement come into
68	78	so the licensing choice is up to the hiring entity.	78	play and so the licensing choice is up to the hiring entity.
69			79
70			80	How can I choose between environments?
71			81
72			82	You can have as many environments as you want in ``environments.yaml`` and
73			83	set one as the default either by specifying
74			84
75			85	``default: default-env-name``
76			86
77			87	or via a ``JUJU_ENV`` environment variable. Last but not least the ``juju``
78			88	subcommands accept an ``-e`` parameter that can be used to specify the name
79			89	of the desired environment.
80	79		90
81	80	How can I contact the juju team?	91	How can I contact the juju team?
82	81		92