<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14354" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/14354?output=omeka-xml" accessDate="2026-05-01T17:53:36+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97794">
              <text>Towards Automated and Optimized Security Orchestration in Cloud SLA</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97795">
              <text>Cloud Computing; Orchestration; Security; Service Level Agreement</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97796">
              <text>In cloud computing, providers pool their resources and make them available to customers. Next-generation computer scientists are flocking to the cutting-edge field of cloud computing for their research and exploration of uncharted territory. There are still several barriers that cloud service providers must overcome in order to provide cloud services in accordance with service level agreements. Each cloud service provider aspires to achieve maximum performance as per Service Level Agreements (SLAs), and this is especially true when it comes to the delivery of services. A cloud service level agreement (SLA) guarantees that cloud service providers will satisfy the needs of large businesses and offer their clients with a specified list of services. The authors offer a web service level agreementinspired approach for cloud service agreements. We adopt patterns and antipatterns to symbolize the best and worst practices of OCCI (Open Cloud Computing Interface Standard), REST (Representational State Transfer), and TOSCA (Topology and Orchestration Specification for Cloud Applications) with DevOps solutions, all of which API developers should bear in mind when designing APIs. When using this method, everything pertaining to the cloud service, from creation to deployment to measurement to evaluation to management to termination, may be handled mechanically. When distributing resources to cloud apps, our system takes into account the likelihood of SLA breaches and responds by providing more resources if necessary. We say that for optimal performance, our suggested solution should be used in a private cloud computing setting. As more and more people rely on cloud computing for their day-to-day workloads, there has been a corresponding rise in the need for efficient orchestration and management strategies that foster interoperability.  2023 International Journal on Recent and Innovation Trends in Computing and Communication. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97797">
              <text>Singh S.; Kumar Bharti A.; Pandey H.; Kumar Yadav R.; Sharma D.; Shanker N.R.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="97798">
              <text>International Journal on Recent and Innovation Trends in Computing and Communication, Vol-11, No. 3, pp. 215-222.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="97799">
              <text>Auricle Global Society of Education and Research</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97800">
              <text>2023-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="97801">
              <text>&lt;a href="https://doi.org/10.17762/ijritcc.v11i3.6339" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.17762/ijritcc.v11i3.6339&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85156087737&amp;amp;doi=10.17762%2Fijritcc.v11i3.6339&amp;amp;partnerID=40&amp;amp;md5=17452575a6cc4701c65778fd5ec01b4b" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85156087737&amp;amp;doi=10.17762%2fijritcc.v11i3.6339&amp;amp;partnerID=40&amp;amp;md5=17452575a6cc4701c65778fd5ec01b4b&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97802">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="97803">
              <text>ISSN: 23218169</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97804">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97805">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="97806">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="97807">
              <text>Singh S., Research Scholar, Computer Science and Engineering, Maharishi University of Information and Technology, U.P., Lucknow, India; Kumar Bharti A., School of Computer Application, Babu Banarasi Das University, Lucknow, U.P., Lucknow, India; Pandey H., Computer Science and Engineering, Lucknow University, U.P., Lucknow, India; Kumar Yadav R.; Sharma D., School of Business Management, Christ University, U.P., Ghaziabad, India; Shanker N.R., Computer Science and Engineering, Aalim Muhamed Salegh College of Engineering, Tamil Naidu, Chennai, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
