FOG COMPUTING

Made By- Ravi Shankar Singh

M.Tech (Comp. Techology)
 FOG COMPUTING
• Decentralized computing infrastructure in which data, compute,
storage and applications are distributed in the most logical, efficient
place between the data source and the cloud.
• Goal of fogging is to improve efficiency and reduce the amount of data
transported to the cloud for processing, analysis and storage.
• Critical component to IOT Applications
• Data filtering to reduce traffic
• Consolidate/compress messages to optimize for network
• Ability to react right at the edge when backhaul to Cloud is not available
 IOX
The Cisco IOx application environment
combines IoT application execution within
the fog, secure connectivity with Cisco IOS
Software, and powerful services for rapid,
reliable integration with Internet of Things
(IoT) sensors and the cloud.
IOx is an end-to-end application
enablement framework that aims to
provide application hosting capabilities for
different application types in a consistent
and uniform manner on all Cisco network
platforms.
IOX ARCHITECTURE
IOX DEVELOPMENT / DEPLOYMENT FLOW
 RESOURCE CONSTRAIN CONSIDERATION
• Bear in mind fog computing happens on Cisco edge routers which typically has limited resource,
thus while design the application, choose the proper language between c, python, or java. As an
example:
• IR829
• CPU: Intel Atom C2308 (1M Cache, 1.25 GHz), Dual Core, X86 64bit.
1 Core for IOS , 0.5 Core for VDS, 0.5 Core for GOS
• Memory: 2GB DDR3 totally; 1GB for GOS (700M for applications)
• Storage: 8GB eMMC totally; 3GB for GOS (800MB for applications)

• IOxSandbox
• OVA Installation: 1vCPU, 2GB RAM, 25GB HD, and ESXi5.0+
• IOx Sandbox environment is meant to be a IOx node for developers to play with ioxclient, Fog Director and
deploy their applications. There are several limitations such as physical interfaces and performance
difference.
 GLOBAL PRICE LIST
MODEL Family RAM FLASH PRICE
IR829GW-LTE-GA-EK9 IR 829 2 GB 4 GB /8GB $3000

IR809G-LTE-GA-K9 IR 809 2 GB 4 GB /8GB $1900

C819HG-U-K9 C 819 512 MB 256 MB $1900
C841M-8X/K9 800M 512 MB 2 GB $1350
C891-k9 890M 512 MB 256 MB $1400
ASR1000-RP2 ASR 8/16 GB - $
1000 31000
ISR4351/K9 4000 4/16GB 4/16GB $ 8000
IOX-CORE-829/809-3Y $2000
IOX-CORE-829/809-5Y $3000

# IOX CORE is a IOx and Fog Director license for respective routers family
# http://itprice.com/cisco-gpl/iox
 IOX APPLICATION DEVELOPMENT
CONSIDERATIONS
• Native/Container apps: These applications are designed to run natively on the Host OS
and are OS dependent. These applications are isolated from each other using isolation
capabilities provided by the Host OS (such as LXC in the case of Linux). The apps are
composed of application codes, 3rd party dependent libraries, native binaries (and entire
root file system, minus the kernel, in the case of LXC) packaged into one archive.
• PaaS style apps: These applications are more portable and self contained, typically
developed using dynamic languages such as Java, Ruby, Python etc, and are designed to
run in specific PaaS frameworks, (OS independent)
• VM packaged apps: These are applications packaged as virtual machines, that is, the
virtual machine that contains OS (kernel + root file system), libraries, and application
code packaged into one package.
CONTAINER AND PAAS STYLE APPLICATIONS
GUIDANCE
Container Style Applications: PaaS Style Applications:
• Tied to Host OS architecture • Self-contained apps, portable

• Total isolation from other apps (via LXC ) • Write-once, deploy across IoTplatforms

• Limited control on life-cycle activity • Python, Java, etc

management
 PACKAGING/FILE STRUCTURE
• An IOx application package shall consist of:
• ONE package descriptor file named as "package.yaml" and should be present in the
root of the package
• ONE tar.gz envelope containing application or service artifacts with the name
"artifacts.tar.gz". These artifacts may be binaries, application code, application
libraries, virtual disks, rootfs etc., More details about this in the below sections.
• zero or one application configuration file named as "package_config.ini". If present,
should be in the root of the package.
• zero or one application manifest named as "package.mf". If present, should be in the
root of the package.
• zero of one certificate containing signing information named as "package.cert". If
present, should be in the root of the package.
 FOG DIRECTOR GUIDANCE
• HW/SW Specification
• 1vCPU, 2GB RAM, 25GB HD, and Ubuntu 14.04.01

• Application Management
• Upload Application
• Publish Application
• Install/Uninstall Application
• Deploy Application to Device
• Start/Stop Application

• Device Management
• Add/Remove Device
• Device Information
DEVNET IOX SERVICE