upstream/ipython Commit - r4062:d11c4497

10

All Connections

10

All Connections

11

===============

11

===============

12

13

The Parallel Computing code is currently under development in IPython's newparallel_

14

branch on GitHub.

15

16

.. _newparallel: http://github.com/ipython/ipython/tree/newparallel

17

18

The IPython cluster consists of a Controller, and one or more each of clients and engines.

13

The IPython cluster consists of a Controller, and one or more each of clients and engines.

19

The goal of the Controller is to manage and monitor the connections and communications

14

The goal of the Controller is to manage and monitor the connections and communications

20

between the clients and the engines. The Controller is no longer a single process entity,

15

between the clients and the engines. The Controller is no longer a single process entity,

21

but rather a collection of processes - specifically one Hub, and 3 (or more) Schedulers.

16

but rather a collection of processes - specifically one Hub, and 4 (or more) Schedulers.

22

17

23

It is important for security/practicality reasons that all connections be inbound to the

18

It is important for security/practicality reasons that all connections be inbound to the

24

controller processes. The arrows in the figures indicate the direction of the

19

controller processes. The arrows in the figures indicate the direction of the

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

             All Connections
             ===============
-            The Parallel Computing code is currently under development in IPython's newparallel_
-            branch on GitHub.
-            .. _newparallel: http://github.com/ipython/ipython/tree/newparallel
             The IPython cluster consists of a Controller, and one or more each of clients and engines.
             The goal of the Controller is to manage and monitor the connections and communications
             between the clients and the engines.  The Controller is no longer a single process entity,
-            but rather a collection of processes - specifically one Hub, and 3 (or more) Schedulers.
+            but rather a collection of processes - specifically one Hub, and 4 (or more) Schedulers.
             It is important for security/practicality reasons that all connections be inbound to the
             controller processes. The arrows in the figures indicate the direction of the