Cloud: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
h2. Introduction


The purpose of this page is to gather the information related to using Qt in conjunction with Cloud computing. Some of the content and Qt framework development goals are the same as described in the "Qt and Web Services":http://developer.qt.nokia.com/wiki/Qt_and_Web_Services wiki article but with the distinction that the Web Services article focuses more on interfacing most common existing Web Services (such as Facebook, Twitter, DropBox etc.). This page focus should be in using Cloud computing resources as the backend of existing Qt application or creating new Qt based services and applications that utilize for example Cloud storage.
== Introduction ==
 
The purpose of this page is to gather the information related to using Qt in conjunction with Cloud computing. Some of the content and Qt framework development goals are the same as described in the [[Qt and Web Services]] wiki article but with the distinction that the Web Services article focuses more on interfacing most common existing Web Services (such as Facebook, Twitter, DropBox etc.). This page focus should be in using Cloud computing resources as the backend of existing Qt application or creating new Qt based services and applications that utilize for example Cloud storage.


== Using Cloud Services from Qt applications ==
== Using Cloud Services from Qt applications ==
Line 7: Line 8:
From the Qt application functionality point of view most interesting Cloud services are related to using Cloud hosted application back-ends or using cloud as the data storage. The Cloud services can be provided by specialized providers, or internally within the organization using the application – same principles and building blocks apply to both. Cloud Services are usually divided into Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS). Since Qt is not a web application development framework as such the focus is primarily on Platform and Infrastructure services. The Cloud services typically applicable for Qt based solutions include:
From the Qt application functionality point of view most interesting Cloud services are related to using Cloud hosted application back-ends or using cloud as the data storage. The Cloud services can be provided by specialized providers, or internally within the organization using the application – same principles and building blocks apply to both. Cloud Services are usually divided into Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS). Since Qt is not a web application development framework as such the focus is primarily on Platform and Infrastructure services. The Cloud services typically applicable for Qt based solutions include:


'''Platform (PaaS)'''<br />* Data storage (Blob, Table Storage and Relational Database Storage)<br />* Queue<br />* Identity and Access Management<br />'''Infrastructure (IaaS)'''<br />* Compute<br />* Network
'''Platform (PaaS)'''
* Data storage (Blob, Table Storage and Relational Database Storage)
* Queue
* Identity and Access Management
'''Infrastructure (IaaS)'''
* Compute
* Network


Interfacing web applications such as Facebook, Twitter and LinkedIn from Qt application can be considered as SaaS type of access. Naming aside, also that level is important and the Cloud services need to allow this to be accomplished easily.
Interfacing web applications such as Facebook, Twitter and LinkedIn from Qt application can be considered as SaaS type of access. Naming aside, also that level is important and the Cloud services need to allow this to be accomplished easily.
Line 21: Line 28:
As an example of cloud service provider offering let’s investigate two popular cloud services Amazon AWS and Microsoft Azure.
As an example of cloud service provider offering let’s investigate two popular cloud services Amazon AWS and Microsoft Azure.


|''. |''. '''Amazon'''|_. '''Azure'''|<br /> | Data Storage - Blob | Simple Storage Service (S3), &quot;REST API&amp;quot;:http://docs.amazonwebservices.com/AmazonS3/latest/API/APIRest.html | Blob storage &quot;REST API&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/dd135733.aspx|<br /> | Data Storage - Table | SimpleDB, &quot;REST API&amp;quot;:http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/MakingRESTRequests.html | Azure Table Storage &quot;REST API&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/dd179423.aspx|<br /> | Relational Database Storage| Relational Database Service (RDS), MySQL or Oracle DB, &quot;Getting Started Guide&amp;quot;:http://docs.amazonwebservices.com/AmazonRDS/latest/GettingStartedGuide/| Azure SQL Storage, Microsoft SQL Server, &quot;Introducing SQL Azure Database&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/ee336230.aspx|<br /> | Queue | Simple Queue Service, &quot;WSDL API&amp;quot;:http://docs.amazonwebservices.com/AWSSimpleQueueService/latest/APIReference/Welcome.html | Windows Azure Queues, &quot;REST API&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/dd179363.aspx |<br /> | Identity &amp; Access Management | AWS Identity and Access Management (IAM), &quot;WSDL API&amp;quot;:http://aws.amazon.com/iam/ | Access Control Service (ACS), Several Access control features, See &quot;Overview of Access Control&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/dd582780.aspx for details|<br /> | Authentication in REST API’s | &quot;HMAC-SHA1 (deprecated) or HMAC-SHA256 based signature and AWS Access Key&amp;quot;:http://aws.amazon.com/articles/1928 | &quot;HMAC-SHA256 based authorization header&amp;quot;:http://msdn.microsoft.com/en-us/library/windowsazure/dd179428.aspx |
{| class="wikitable"
!
! Amazon
! Azure
|-
| Data Storage - Blob  
| Simple Storage Service (S3), [http://docs.amazonwebservices.com/AmazonS3/latest/API/APIRest.html REST API]
| Blob storage [http://msdn.microsoft.com/en-us/library/windowsazure/dd135733.aspx REST API]
|-
| Data Storage - Table  
| SimpleDB, [http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/MakingRESTRequests.html REST API]
| Azure Table Storage [http://msdn.microsoft.com/en-us/library/windowsazure/dd179423.aspx REST API]
|-
| Relational Database Storage
| Relational Database Service (RDS), MySQL or Oracle DB, [http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.html Getting Started Guide]
| Azure SQL Storage, Microsoft SQL Server, [https://redblink.com/setup-nfs-server-provisioner-kubernetes/ setting up nfs provisioning server in kubernetes] [http://msdn.microsoft.com/en-us/library/windowsazure/ee336230.aspx Introducing SQL Azure Database]
|-
| Queue  
| Simple Queue Service, [http://docs.amazonwebservices.com/AWSSimpleQueueService/latest/APIReference/Welcome.html WSDL API]
| Windows Azure Queues, [http://msdn.microsoft.com/en-us/library/windowsazure/dd179363.aspx REST API]
|-
| Identity & Access Management  
| AWS Identity and Access Management (IAM), [http://aws.amazon.com/iam/ WSDL API]
| Access Control Service (ACS), Several Access control features, See [http://msdn.microsoft.com/en-us/library/windowsazure/dd582780.aspx Overview of Access Control] for details
|-
| Authentication in REST API’s  
| [http://aws.amazon.com/articles/1928 HMAC-SHA1 (deprecated) or HMAC-SHA256 based signature and AWS Access Key]
| [http://msdn.microsoft.com/en-us/library/windowsazure/dd179428.aspx HMAC-SHA256 based authorization header]
|}


== Requirements for Qt Framework development ==
== Requirements for Qt Framework development ==
Line 29: Line 64:
* JSON
* JSON
** Parsing through QScriptEngine already supported  
** Parsing through QScriptEngine already supported  
** Discussion about adding JSON support to QtCore module in qt-project &quot;development mailing list&amp;quot;:http://lists.qt.io/pipermail/development/2011-December/000813.html, and the initial patch has already been &quot;merged&amp;quot;:http://codereview.qt.io/#change,13542  
** Discussion about adding JSON support to QtCore module in qt-project [http://lists.qt-project.org/pipermail/development/2011-December/000813.html development mailing list], and the initial patch has already been [http://codereview.qt.io/#change,13542 merged]
** JSON datamode for QML: &quot;QTBUG-12117&amp;quot;:https://bugreports.qt.nokia.com/browse/QTBUG-12117  
** JSON datamode for QML: [https://bugreports.qt.nokia.com/browse/QTBUG-12117 QTBUG-12117]
* Hash-based Message Authentication Code (HMAC)
* Hash-based Message Authentication Code (HMAC)
** HMAC- SHA256 needed for generating the authorization. &quot;QCryptographicHash&amp;quot;:http://developer.qt.nokia.com/doc/qcryptographichash.html should be extended to support SHA2 family (especially SHA256) &quot;QTBUG-2068&amp;quot;:https://bugreports.qt.nokia.com/browse/QTBUG-2068 and there should be a way for creating the message authentication header &quot;QTBUG-904&amp;quot;:https://bugreports.qt.nokia.com/browse/QTBUG-904. Code snippet for HMAC-SHA1 in &quot;DevNet&amp;quot;:http://developer.qt.nokia.com/wiki/HMAC-SHA1  
** HMAC- SHA256 needed for generating the authorization. [http://developer.qt.nokia.com/doc/qcryptographichash.html QCryptographicHash] should be extended to support SHA2 family (especially SHA256) [https://bugreports.qt.nokia.com/browse/QTBUG-2068 QTBUG-2068] and there should be a way for creating the message authentication header [https://bugreports.qt.nokia.com/browse/QTBUG-904 QTBUG-904]. Code snippet for HMAC-SHA1 in [http://developer.qt.nokia.com/wiki/HMAC-SHA1 DevNet]
* oAUTH
* oAUTH
** Discussion and planning ongoing. See status: &quot;QTBUG-6229&amp;quot;:https://bugreports.qt.nokia.com/browse/QTBUG-6229
** Discussion and planning ongoing. See status: [https://bugreports.qt.nokia.com/browse/QTBUG-6229 QTBUG-6229]


=== Qt SDK’s for different cloud services ===
=== Qt SDK’s for different cloud services ===
Line 42: Line 77:
=== Generic Qt Cloud API ===
=== Generic Qt Cloud API ===


One possible approach would be creating a generic Qt Cloud API that would hide the Cloud service provider specific implementation. This approach would be similar to &quot;Simple Cloud API initiative&amp;quot;:http://simplecloud.org/.
One possible approach would be creating a generic Qt Cloud API that would hide the Cloud service provider specific implementation. This approach would be similar to [http://simplecloud.org/ Simple Cloud API initiative].


=== Tools ===
=== Tools ===


* IDE Templates
* IDE Templates
* Sample Applications (Similar as &quot;QTBUG-13353&amp;quot;:https://bugreports.qt.nokia.com/browse/QTBUG-13353)
* Sample Applications (Similar as [https://bugreports.qt.nokia.com/browse/QTBUG-13353 QTBUG-13353])
* Documentation
* Documentation

Latest revision as of 13:36, 8 September 2020

Introduction

The purpose of this page is to gather the information related to using Qt in conjunction with Cloud computing. Some of the content and Qt framework development goals are the same as described in the Qt and Web Services wiki article but with the distinction that the Web Services article focuses more on interfacing most common existing Web Services (such as Facebook, Twitter, DropBox etc.). This page focus should be in using Cloud computing resources as the backend of existing Qt application or creating new Qt based services and applications that utilize for example Cloud storage.

Using Cloud Services from Qt applications

From the Qt application functionality point of view most interesting Cloud services are related to using Cloud hosted application back-ends or using cloud as the data storage. The Cloud services can be provided by specialized providers, or internally within the organization using the application – same principles and building blocks apply to both. Cloud Services are usually divided into Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS). Since Qt is not a web application development framework as such the focus is primarily on Platform and Infrastructure services. The Cloud services typically applicable for Qt based solutions include:

Platform (PaaS)

  • Data storage (Blob, Table Storage and Relational Database Storage)
  • Queue
  • Identity and Access Management

Infrastructure (IaaS)

  • Compute
  • Network

Interfacing web applications such as Facebook, Twitter and LinkedIn from Qt application can be considered as SaaS type of access. Naming aside, also that level is important and the Cloud services need to allow this to be accomplished easily.

In cases where you have an existing Qt application that uses a relational database the easiest way to utilize Cloud storage is by using Relational Database Storage services. These services provide the database interface using the same mechanisms as databases usually provide remote access. Of course firewall and other security aspects must be taken into consideration.

If you already have a client-server based application implemented in Qt and want to use distributed and scalable computing environment, the most natural way is to use Virtualized Cloud Computing environment like Amazon EC2 or Azure Compute.

Many Cloud services expose REST API’s for managing and accessing the actual service. From Qt perspective REST based API’s are easier to use in a since Qt already includes almost all needed functionality. There are available Qt implementations also for accessing e.g. SOAP based services.

Cloud services per provider mapping

As an example of cloud service provider offering let’s investigate two popular cloud services Amazon AWS and Microsoft Azure.

Amazon Azure
Data Storage - Blob Simple Storage Service (S3), REST API Blob storage REST API
Data Storage - Table SimpleDB, REST API Azure Table Storage REST API
Relational Database Storage Relational Database Service (RDS), MySQL or Oracle DB, Getting Started Guide Azure SQL Storage, Microsoft SQL Server, setting up nfs provisioning server in kubernetes Introducing SQL Azure Database
Queue Simple Queue Service, WSDL API Windows Azure Queues, REST API
Identity & Access Management AWS Identity and Access Management (IAM), WSDL API Access Control Service (ACS), Several Access control features, See Overview of Access Control for details
Authentication in REST API’s HMAC-SHA1 (deprecated) or HMAC-SHA256 based signature and AWS Access Key HMAC-SHA256 based authorization header

Requirements for Qt Framework development

Identified enhancements to existing modules

  • JSON
    • Parsing through QScriptEngine already supported
    • Discussion about adding JSON support to QtCore module in qt-project development mailing list, and the initial patch has already been merged
    • JSON datamode for QML: QTBUG-12117
  • Hash-based Message Authentication Code (HMAC)
    • HMAC- SHA256 needed for generating the authorization. QCryptographicHash should be extended to support SHA2 family (especially SHA256) QTBUG-2068 and there should be a way for creating the message authentication header QTBUG-904. Code snippet for HMAC-SHA1 in DevNet
  • oAUTH
    • Discussion and planning ongoing. See status: QTBUG-6229

Qt SDK’s for different cloud services

Each of the Cloud services need a separate API implementation (often called as SDK’s). These provider specific API implementations can be the API’s that the application developer uses or those can be wrapped as plugins for generic Qt Cloud API or accessed through existing Qt Modules. At concept level for example QFile maps to Amazon S3 Objects and QDir maps to S3 Buckets, however for example the QFile is synchronous whereas Cloud Blob storage API should be asynchronous.

Generic Qt Cloud API

One possible approach would be creating a generic Qt Cloud API that would hide the Cloud service provider specific implementation. This approach would be similar to Simple Cloud API initiative.

Tools

  • IDE Templates
  • Sample Applications (Similar as QTBUG-13353)
  • Documentation