CHAPTER FOUR PROPOSED CLOUD BASED FRAMEWORK 4

CHAPTER FOUR
PROPOSED CLOUD BASED FRAMEWORK
4.1. Backgrounds of the Framework
This research has aimed to design cloud-based framework that serves the agricultural sector in Ethiopia. To do this, Firstly, we have studied how the current agricultural sector operations are performed and the agricultural activities which are possible for the integrated service delivery. Secondly, the cloud computing technology which helps to develop the framework has been identified. The main objective of this framework is:- to collect data or information from various users, to analyze the information and create various classes based on the information required, to store the classified information in cloud repository for future use. to response the user query based on information stored in repository.
In literature review and result in discussion section, we have presented the requirements to develop the proposed solution. Based on that assessment the public cloud deployment model is chosen as the deployment model and software as service models are chosen as a cloud service delivery models. In this proposed system we have used multiple data center architecture to protect the entire site/application from being negatively affected by some type of network/power failure, lack of available resources, or service outage that’s specific to a particular datacenter.
4.2. Building the Framework
The proposed framework is the key mechanism that ensures the resource manager can assist large
amount of request without violating SLA. The service of agriculture divided into three types
SaaS(software as a service), PaaS(platform as a service), IaaS( Infrustrure as a service). In SaaS,
user interface is designed in which user can interact with and Aneka is a .Net based as a scalable
cloud middleware between cloud subsystem and user subsystem. We deployed agriculture web
service of Agro-Info to provide user interface through Aneka cloud application platform in which
user can access service from any geographical location and information is classified, stored into
loud repositories and retrieved based on user request at platform level. In IaaS, resource manager
manages the resource based on the identified QoS requirements of a particular request. Framework
of Agro-Info comprises following two subsystems: i) user subsystem and ii) cloud subsystem.
4.2.1. User Subsystem
This subsystem delivers a user interface, in which different type of users interacting with Agro-Info to provide and get useful information about agriculture based on different domains. We have considered different types of information domains in agriculture: crop, weather, soil, pest, fertilizer, productivity, market status, irrigation, cattle and equipment. Users are basically classified in three categories: agriculture expert, agriculture officer and farmer. Agriculture expert shares professional knowledge by answering the user queries and updates the agriculture database based on the latest research done in the field of agriculture with respect to their domain. Agriculture officers are the government officials those provides the latest information about new agriculture policies, schemes and rules passed by the government. Farmer is an important entity of Agro -Info who can take maximum advantage by asking their queries and getting reply after analysis. Users can monitor any data related to their domain and get their response without visiting the agriculture help center. It integrates the different domains of agriculture with Agro-Info. Agro-Info does not require any technical expertise to use this system. The information or queries received from user(s) are forwarded to cloud repository to update and response is send back to particular user on their preconfigured devices (tablets, mobile phones, laptops etc.) via internet.
4.2.2. Cloud Subsystem
This subsystem contains the platform in which agriculture web service is hosted on a cloud. Agriculture web service allows to process the agriculture information provided by users (agriculture expert, agriculture officer and farmer) of different domains in agriculture sector. These details are stored in cloud repository in different classes for different domains with unique identification number. The information is monitored, analyzed and processed continuously by Agro-Info. We have designed different classes for every domain and sub classes for further categorization of information. In storage repository, user data is categorized based on different predefined classes of every domain. This information is further forwarded to agriculture experts and agriculture officers for final validation through preconfigured devices. Further, a number of users can use this cloud-based agriculture service.
Agro-Info allows user to upload the data related to different domains of agriculture through preconfigured devices and classified them based on the domains specified in database.

FIGURE 4.1. PROPOSED FRAMEWORK 1
Initially, Monitors are used to collect the information for monitoring continuously performance variations by comparing expected and actual performance. Actual information about performance is observed based QoS parameters and transfers this information to next module for further analysis.
QoS manager identifies the QoS requirements based on the number and type of user requests. Based on QoS requirements, resource manager identifies resource requirements and allocates and executes the resources at infrastructure level. Performance monitor is used to verify the performance of system and maintain it. Analyze and plan module start analyzing the information received from monitoring module and make a plan for adequate actions for corresponding user request. Numbers of users upload their data of different domains from which Agro-Info selects only relevant information and maintains this as a gathered Target Data. In this sub process, target datasets are created based on the relevant information that will further be considered for analysis detail information.