RACK - Revision history

Tetsuya-oikawa at 07:10, 19 October 2015

2015-10-19T07:10:44Z

Takehirokaneko at 03:57, 18 December 2014

2014-12-18T03:57:14Z

Takehirokaneko at 06:44, 6 October 2014

2014-10-06T06:44:04Z

Takehirokaneko at 06:31, 6 October 2014

2014-10-06T06:31:52Z

Show changes

Takehirokaneko at 03:02, 6 October 2014

2014-10-06T03:02:47Z

Takehirokaneko at 02:56, 6 October 2014

2014-10-06T02:56:40Z

Takehirokaneko at 06:01, 22 July 2014

2014-07-22T06:01:13Z

Takehirokaneko at 10:44, 18 July 2014

2014-07-18T10:44:29Z

Takehirokaneko: /* VM like a Linux process? */

2014-07-18T10:44:10Z

‎VM like a Linux process?

Takehirokaneko at 10:42, 18 July 2014

2014-07-18T10:42:52Z

@@ Line 13: / Line 13: @@
 |-
 | Source code
-| https://github.com/stackforge/rack
+| https://github.com/openstack/rack
+|
 |-
 | Deployment guide
-| https://github.com/stackforge/rack/tree/master/tools/setup
+| https://github.com/openstack/rack/tree/master/tools/setup
-| https://github.com/stackforge/rack/blob/master/tools/setup/README_ja.md
+| https://github.com/openstack/rack/blob/master/tools/setup/README_ja.md
 |-
 | Sample applications
@@ Line 29: / Line 29: @@
 |-
 | Python RACK client
-| https://github.com/stackforge/python-rackclient
+| https://github.com/openstack/python-rackclient
+|
 |}
@@ Line 62: / Line 62: @@
 Also it provides API to control data communication and sharing.
 Applications have to be scripted by order of calling the APIs.
-The RACK also offers libraries [https://github.com/stackforge/python-rackclient|python-rackclient] for using APIs.
+The RACK also offers libraries [https://github.com/openstack/python-rackclient|python-rackclient] for using APIs.
 It is very easy to write OpenStack Native Application codes by using the libraries.
 The RACK may be recognized as framework for writing OpenStack Native Application.

@@ Line 22: / Line 22: @@
 | Sample applications
+|
-* https://github.com/stackforge/rack/tree/master/tools/sample-apps/montecarlo
+* https://github.com/ctc-g/rack-sample-apps/tree/master/montecarlo
-* https://github.com/stackforge/rack/blob/master/tools/sample-apps/shell-like
+* https://github.com/ctc-g/rack-sample-apps/tree/master/shell-like
+|
-* https://github.com/stackforge/rack/blob/master/tools/sample-apps/montecarlo/README_ja.md
+* https://github.com/ctc-g/rack-sample-apps/tree/master/montecarlo/README_ja.md
-* https://github.com/stackforge/rack/blob/master/tools/sample-apps/shell-like/README_ja.md
+* https://github.com/ctc-g/rack-sample-apps/tree/master/shell-like/README_ja.md
 |-
 | Python RACK client
@@ Line 50: / Line 50: @@
 Please take a look at the sample programs to experience RACK!
-* https://github.com/stackforge/rack/tree/master/tools/sample-apps/montecarlo
+* https://github.com/ctc-g/rack-sample-apps/tree/master/montecarlo
-* https://github.com/stackforge/rack/tree/master/tools/sample-apps/shell-like
+* https://github.com/ctc-g/rack-sample-apps/tree/master/shell-like
 [[File:RACK-Process-Image.png]]
@@ Line 159: / Line 159: @@
 As tips on how to use RACK, some sample applications are available.
 We advise you to try these sample applications first and experience the OpenStack Native Application.
-* https://github.com/stackforge/rack/tree/master/tools/sample-apps/montecarlo
+* https://github.com/ctc-g/rack-sample-apps/tree/master/montecarlo
-* https://github.com/stackforge/rack/tree/master/tools/sample-apps/shell-like
+* https://github.com/ctc-g/rack-sample-apps/tree/master/shell-like

@@ Line 102: / Line 102: @@
 * PID, PPID
-The ID of the parent ID and is assigned to each process.
+Each process holds its own ID (PID) and the parent's IP (PPID).
 These IDs represent the parent-child relationship between processes.
@@ Line 120: / Line 120: @@
 Our future plan includes followings:
-* rack-api runs as Linux process in OpenStack controller node like nova-api.
+* '''rack-api runs as Linux process in OpenStack controller node like nova-api.'''
-* rack-proxy runs as Linux process in OpenStack network node like nutron-ns-metadata-proxy.
+* '''rack-proxy runs as Linux process in OpenStack network node like nutron-ns-metadata-proxy.'''
 Since this area is closely related to the OpenStack core project, they are deployed as VM at the moment.

@@ Line 1: / Line 1: @@
 = RACK (Real Application Centric Kernel) =
 == Project Resources ==
@@ Line 31: / Line 32: @@
+|
 |}
 == OpenStack Native Application ==

@@ Line 1: / Line 1: @@
 = RACK (Real Application Centric Kernel) =
 == OpenStack Native Application ==
@@ Line 104: / Line 134: @@
 For customers, it's less expensive to use a lot of low-spec instances to process data fast than a high spec instance.
 For cloud providers, a large amount of resources will come to be consumed.

← Older revision		Revision as of 06:01, 22 July 2014
Line 91:		Line 91:


−	== ~~Bench Mark~~ of OpenStack Native Application ==	+	== Benchmark of OpenStack Native Application ==
		+
		+	We conducted a benchmark test of OpenStack Native Application that behaves like the first example of above usecases.
		+	The following graph shows the result.
		+	We can see one of the characteristics of OpenStack Native Application from this graph.
		+	This application scales worker processes out depending on the number of dataset, and these processes work in parallel, so the total execution time is held constant.
		+	Theoretically, the more it scales out, the shorter the execution time is.
		+
		+	[[File:RACK-Benchmark.png]]
		+
		+	It's good for both customers and cloud providers.
		+	For customers, it's less expensive to use a lot of low-spec instances to process data fast than a high spec instance.
		+	For cloud providers, a large amount of resources will come to be consumed.

← Older revision		Revision as of 10:44, 18 July 2014
Line 34:		Line 34:

	[[File:RACK-Process-Image.png]]		[[File:RACK-Process-Image.png]]
		+

	== Features ==		== Features ==

← Older revision		Revision as of 10:44, 18 July 2014
Line 33:		Line 33:
	Additionally, when the process executes "Fork", a child process is launched, and given PID and a parent PID (PPID).		Additionally, when the process executes "Fork", a child process is launched, and given PID and a parent PID (PPID).

		+	[[File:RACK-Process-Image.png]]

	== Features ==		== Features ==

@@ Line 15: / Line 15: @@
 We named the application with such behavior “OpenStack Native Application”.
 == What is RACK? ==
-RACK enables an application to control VMs like a linux process.
+RACK enables an application to control VMs like a Linux process.
 It provides an application with PID, parent-child relationship, “Fork” / “Kill” VMs capabilities, interVM communication and message exchange without VM’s IP address.
 Ultimately, RACK enables you to implement a large scale distributed system in a variety of programming languages on OpenStack.
-* You can implement a new architecture application. For example, you can build an application that calculates the necessary amount of computing resource(i.e. instance) depending on the data to process and launches additional instances dynamically. Then, the data will be processed very quickly since these instances work in parallel. This new architecture application is suitable for processing a large amount of data.
+== VM like a Linux process? ==
-* You can integrate existing system such as batch system with Hadoop and Web application using RACK. For example, RACK enables you to deploy Hadoop cluster easily and add autoscale function to your Web applications.
+Look at the picture below.
@@ Line 33: / Line 38: @@
 RACK provides some features as follows.
-* '''Additional attributes to an instance'''<br />In order to treat an instance like a Linux process, RACK adds some additional attributes such as PID(process ID), PPID(parent's process ID) and GroupID(process group ID) to it. In the rest of the document, instance is called "process". This enables to control OpenStack as program resource easily. For example, when a process wants to create an additional process, the process executes fork method in the program. Then, a new process(i.e. child process) is created with the same image as well as connected to the same network with its parent process's. These processes are associated with a GroupID.
+[[File:RACK-Features.png]]
 * '''Interprocess Communication'''<br />Processes can send a message with each other without knowing each other's IP address.
-* '''Shared Memory'''<br />This enables to store data in key-value pairs. The shared memory space is allocated per a GroupID and each space is isolated. Process can add, get, edit and delete a key-value data.
+* '''Shared Memory'''<br />Processes can share the data such as the data to process and their outputs.
-* '''File System'''<br />This enables to store files. The file system is allocated per a GroupID and each one is isolated. Process can add, get and delete files.
+* '''Compiler'''<br />VM image creation automation tool. Compiler assists you to create VM image adapted RACK.
 == Architecture Overview ==
 [[File:RACK-Architecutre-Overview.png]]
 == Resources ==
 '''SourceCode'''
-* https://github.com/ctc-g/rack
+* https://github.com/stackforge/rack