Oracle Cloud With Azure DevOps Pipelines

Oracle Cloud DevOps
with Azure Pipelines
Johan Louwers
Oracle Chief Enterprise Architect
Copyright © 2021, Oracle and/or its affiliates. All rights reserved. | Johan Louwers – Chief Enterprise Architect @ Oracle

The following is intended to outline our general product direction. It is intended for information purposes only,
and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions.The development, release,
timing, and pricing of any features or functionality described for Oracle’s products may change and remains at
the sole discretion of Oracle Corporation.
Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and prospects
are “forward-looking statements” and are subject to material risks and uncertainties. A detailed discussion of
these factors and other risks that affect our business is contained in Oracle’s Securities and Exchange
Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-Q under the heading
“Risk Factors.”These filings are available on the SEC’s website or on Oracle’s website
at http://www.oracle.com/investor. All information in this presentation is current as of September 2019 and
Oracle undertakes no duty to update any statement in light of new information or future events.
Safe Harbor

Oracle Cloud - DevOps Pipelines
CI/CD pipelines for Cloud DevOps
Moving features from the DevOps community to the user community

Ensuring the versioned state will represent the deployed state

Enforce an automated and assured model by leveraging automation in the form of pipelines

• Github
• Gitlab
• Bitbucket
• Etc…
• Azure DevOps Pipelines
• Jenkins
• Travis CI
• Etc…
• Oracle Cloud
• Any other
target
Presentation Focus

Oracle Cloud DevOps
Connecting Azure Pipelines to
OCI APIs and deployed
components

Connecting Azure and Oracle Cloud
Execution logic of Azure pipelines need to bridge the platform gap between Azure and Oracle Cloud

Option 1 : Leverage Microsoft Hosted Agents1 for both infrastructure and application deployments. Leverage the Oracle Public Cloud APIs for all infra
related deployments. For application deployments this will require a relaxed cloud security model to allow Azure based agents to communicate to targets
inside Oracle Cloud
1) https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
2) https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-linux?view=azure-devops

Option 2 : Leverage a mix of Microsoft Hosted Agents1 for infrastructure deployment and Self Hosted Agents2 (Oracle cloud based) for application
deployments.

Option 3 : Leverage Self Hosted Agents2 (Oracle cloud based) for application AND infrastructure deployments, ensuring all executions are being done
within the context of Oracle Cloud.

• Agents communicate with Azure
Pipelines to determine which job
it needs to run(A), and to report
the logs and job status (B).
• All communication
between the agent and
Azure will be initiated by
the Agent and never by
Azure.
• Self hosted Azure Agents need
to be registered to a pool in
Azure

• Agents communicate with Azure
Pipelines to determine which job
it needs to run(A), and to report
the logs and job status (B).
• All communication
between the agent and
Azure will be initiated by
the Agent and never by
Azure.
• Self hosted Azure Agents need
to be registered to a pool in
Azure
• Agents an leverage all
available Oracle Cloud
compute shapes and
types (VMs, containers or
bare-metal compute)
https://dev.azure.com/{env. name}/{project name}/_settings/agentqueues

• Pipelines can be configured to
use any available pool, including
pools based upon self hosted
agents within Oracle Cloud

• Full pipeline execution will
de done on a agent node
running on Oracle Cloud

• Full pipeline execution will
de done on a agent node
running on Oracle Cloud
• Including checkout data
from version control into
the agent node running on
Oracle Cloud

Oracle Cloud DevOps
Deploying Azure Agents in Oracle
Cloud

• Azure Agents, based upon a VM
are a generic OCI VM and can be
created manually or using
automation in the form of Terraform
or others
• It is required that they are able to
communicate outwards. No
external exposure is required
• It is advised to ensure a “azure
agent image” is available for
deployment with automated
registering / de-registering as part
of the CI/CD strategy
• It is advised to ensure agents are
placed in a secured compartment
with their own dedicated VCN to
ensure strict network
compartmentation
Oracle Cloud - DevOps PipeLines
Deploying Azure Agents in Oracle Cloud

• For manual configuration / initial
creation of your “azure agent
image” the following steps will be
required. All steps can be put into
an automated script with CLI flags
1. Download the agent
2. Configure the agent

• For manual configuration / initial
creation of your “azure agent
image” the following steps will be
required. All steps can be put into
an automated script with CLI flags
1. Download the agent
2. Configure the agent
3. Run the service
(only for testing, should be a service for real use)
4. Verify the agent is
registered

• Additional notes:
• Agents can run on a VM/BM within OCI as well
as on a Kubernetes based platform.
• Agents can run in a container and can be
instructed to auto-stop after a job and maintain a
defined number of running containers. Use
./run.sh --once
• All software and tooling require by the pipeline
logic can be included in your image or ”loaded”
as a pipeline command.
• Azure agent will require git 2.0 client as minimal
requirement when using a GIT repo.
• It is advised to ensure a “azure agent image” is
available for deployment with automated
registering / de-registering as part of the CI/CD
strategy.
• All deployment steps can be automated.

Oracle Cloud DevOps
Connecting Azure Pipelines to
OCI Based Databases &
Infrastructure

Oracle SQLcL
cx_Oracle
• Azure Agents are able to
interact with Oracle Databases
leveraging the tooling you
already familiar with to do
automation
• Ensuring a direct connect
instead a cross cloud connect is
advisable
• Aiming for a software defined
and automated strategy is
advisable
Working with Oracle Databases

Working with Oracle Cloud Infrastructure
interact with Oracle
infrastructure leveraging the
tooling you already familiar with
to do automation
advisable
advisable

Working with Oracle Cloud Infrastructure
interact with Oracle
infrastructure leveraging the
tooling you already familiar with
to do automation
advisable
advisable
• Example of using terraform for
Oracle Cloud in combination
with Azure DevOps

Thank you
Johan Louwers
Oracle – Chief EnterpriseArchitect
Cloud Native Engineering Leadership

Oracle Cloud With Azure DevOps Pipelines

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Oracle Cloud With Azure DevOps Pipelines

Semelhante a Oracle Cloud With Azure DevOps Pipelines (20)

Mais de Johan Louwers

Mais de Johan Louwers (20)

Último

Último (20)

Oracle Cloud With Azure DevOps Pipelines