Uploaded image for project: 'Ansible Cloud Automation'
  1. Ansible Cloud Automation
  2. ACA-1398

ARC VM Connectivity support in Ansible collection for Azure

XMLWordPrintable

    • ARC VM Connectivity support in Ansible collection for Azure
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • ANSTRAT-632 - Phase 2: Azure Content Collection Enhancements
    • ANSTRAT-632Phase 2: Azure Content Collection Enhancements
    • 60% To Do, 20% In Progress, 20% Done

      Background

      Red Hat and Microsoft have business alignment on the need for Azure ARC support. Microsoft wants Azure to manage infrastructure in or outside of the cloud, and Red Hat wants to be able to automate deployment and configuration of that infrastructure. Azure ARC is a pillar of Microsoft's 2022 Azure strategy, and Red Hat can benefit from Microsoft technological and business partnerships by supporting ARC.

      Azure Arc support for virtual machine management over SSH is the first area in which this business alignment will happen. Microsoft desires the ability to bring VM management under support of the Azure umbrella through Arc, and Red Hat wants to enable the connectivity and automation of those connected VMs through Arc as if the nodes are directly routable.

      User Stories

      As an Ansible on Azure customer I can connect to and automate against virtual machines connected to Azure via Azure Arc through Arc support of SSH as if the host were directly routable and could be automated against like a native host in AAP in order for me to be able to use AAP for my VM configuration management through my Arc server inventory.

      Supporting documentation

      <include links to technical docs, diagrams, etc>

      Ready-Ready

      https://docs.google.com/document/d/1dBW492UfCR5JxUvcx6efjYP_ibCdiwGONS-sxDb_SPU/edit# 

      Complete Ready-Ready checklist

      Definition of Done

      Should be agreed upon per team; add/remove/update to reflect:{}

      • CI is running, tests are automated and merged and successful
      • DEV upstream code & tests merged
      • DEV upstream documentation merged
      • DEV downstream build attached to advisory
      • QE - Test plans documented and attached to epic (or link to source)
      • QE - automated tests merged and passing
      • Docs - Downstream documentation is merged
      • PM - all acceptance criteria are met (note: we want to start using the AC specific field, but please fill out below in the meantime)

       

      Note: please also fill out the 'Acceptance Criteria' to indicate functional criteria aka scope, specific to this issue, that should be met in order to 'accept' the work to consider complete. 

            nargaman Nir Argaman
            nargaman Nir Argaman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: