Home

n3phele provides consumers a workspace for performing task processing and service creation & management using cloud resources. The workspace is accessible from a computer desktop or mobile device. n3phele allows the consumer to request execution of commands, where a command specifies the orchestration cloud resources, to enable the following:

• Task based processing Orchestration of a set of activities consuming and producing cloud-based objects using both infrastructure-as-a-service resources and other pre-existing web services. A task primarily produces results as cloud objects. Cloud objects provide a file-like paradigm, accessible via an http(s) protocol and semantic

• Service based offerings Creation and on going management of web accessible service offerings.

The environment builds on familiar concepts borrowed from the personal computer desktop, to provide a workspace that uses cloud resources rather than personal computer resources, as shown in table 1.

         | **PC Desktop** | **Cloud Workspace**

------------ | ---------- | --------------- presentation | Video Adapter | Browser, mobile app shell | BASH, windows desktop | interpreters filesystem | NTFS offering files | Swift, S3, Google desktop offering cloud objects executable | .exe, .jars | AMIs, Glance images Process | process | Virtual machine, web service/REST call Kernel dispatcher, scheduler | windows | n3phele-core

Table 1. Comparison of PC Desktop and Cloud Workspace

n3phele orchestration consists of an inner core responsible for the dispatch of processing of actions. Examples of actions include:

• creation and on going lifecycle management of n virtual machines
• copy a file to/from a cloud repository and a vm
• execute a shell command on a vm
• create a log message
• wait of a set of dependencies to complete
• callback the shell for operations such as sequence scaling

Actions are modeled as productions, with a set of input and output dependencies, corresponding to the creation, deletion or update of context meta-data, virtual machine or cloud objects. The action outputs can be input dependencies for other actions. Execution of an action is blocked until all required dependencies are available allowing a natural parallelism in command execution.

The shell is responsible for reading and interpreting a particular consumer command request, and based on the shell semantics, managing the creation of a set of actions, and maintaining semantics based on the results of particular shell and command specification. One or more types of shell can be responsible for interpreting either task base or service base command requests.

F.A.Q | [Setting up your n3phele account] (https://github.com/n3phele/n3phele-core/wiki/Setting-up-your-n3phele-account)