In today’s technology industry, cloud refers to servers which can be accessed viainternet, and the software and database applications run on the servers [22]. Whereas cloud computing is a concept of delivering the IT resources via internet which is accessed by the users and companies. In these scenarios OpenStack is the widely used cloud software which controls large pool of IT resources like compute, storage and networking which are managed and provisioned through APIs [11]. In this technology the underlying parts are the transport protocols and web servers used for authenticating and provisioning mechanisms.

When stating about its underlying transport protocols, TCP is the default (standard) protocol used behind the functioning of cloud, and HTTP/1.1 version towards actions between Web servers (apache2 and nginx) and browsers [10]. The scope of the thesis is to observe the complexity of replacing TCP with QUIC (Quick UDP Internet Connection) in OpenStack and to observe the performance difference in OpenStack using HTTP/1.1 and HTTP/3.

To observe this complexity, Performance Evaluation has been considered the best way in which the performance can be observed from the terminals. The thesis deals with performance of OpenStack with transport protocols from a Web server supporting HTTP/3 feature.

We prove that its possible to provide the Keystone API via both HTTP/1.1 and HTTP/3. From our results we see that for simple API access HTTP/3 is faster than the HTTP/1.1 and also when the network is subjected to packet loss. The resultstates that there is a path obtained for OpenStack’s Keystone Service to interact with HTTP/3 and the average request-response time (total time) of HTTP/3 is less than that of HTTP/1.1 for accessing Keystone and Token generation even at defined packet loss rates.