Oracle Cloud Migrations

ociWorkeroci-cloud-migrations

Discovery, planning and replication of VMware and EC2 workloads into OCI.

Provider
oci
Kind
Worker
Category
Compute
Properties · 2 set by this component
propertytypevaluesrequiredkind defaultthis component
acceleratorenumnone | gpu | asicnononeinherited
concurrencyinteger—no—inherited
discoveryMethod · component propertyenumautomated | csv-importnoautomatedinherited
fanoutStrategy · advancedenumnone | push | pull | hybridnononeinherited
fanoutThreshold · advancedinteger—no—inherited
idempotentboolean—nofalseinherited
instancesinteger—no—inherited
managedboolean—nofalse▸ true
rateControl · advancedenumnone | fixed | aimdnononeinherited
remoteAgentAppliance · component propertyboolean—notrueinherited
replicationSchedule · component propertyboolean—nofalseinherited
resourceManagerStack · component propertyboolean—notrueinherited
schedulestring—no—inherited
sourceEnvironment · component propertyenumvmware | aws-ec2no—inherited
triggerenumqueue | stream | schedule | batch | manualyes—▸ manual
Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

push-fanout-without-celebrity-path

Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.

  • — all of these hold:
  • — the node's `fanoutStrategy` is "push"
  • — the node's `fanoutThreshold` has no value
  • — the design contains a node of kind graph-database
shared-worker-pool-across-queues

One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.

  • — all of these hold:
  • — the node has more than 1 incoming edge from a queue
  • — the design requirement `isolation.perQueue` is true
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "cloud-migrations", component: "oci-cloud-migrations" }
Other Worker products · 82
SchedulerXalibaba-schedulerxalibabacloudworkerAmazon AppFlowaws-appflowawsworkerAWS B2B Data Interchangeaws-b2b-data-interchangeawsworkerAWS Batchaws-batchawsworkerAWS Glue DataBrewaws-databrewawsworkerAWS DataSyncaws-datasyncawsworkerAWS Deadline Cloudaws-deadline-cloudawsworkerAWS Entity Resolutionaws-entity-resolutionawsworkerAmazon EventBridge Scheduleraws-eventbridge-schedulerawsworkerAWS Fault Injection Serviceaws-fisawsworkerAWS Glue crawleraws-glue-crawlerawsworkerAWS Glue for Ray jobaws-glue-ray-jobawsworkerAWS Application Migration Serviceaws-mgnawsworkerAmazon MSK Connectaws-msk-connectawsworkerAmazon SageMaker AI Training Jobaws-sagemaker-training-jobawsworkerAWS Systems Manageraws-systems-managerawsworkerAWS Thinkbox Deadline 10aws-thinkbox-deadlineawsworkerAWS Glue jobglue-jobawsworkerAzure Automationazure-automationazureworkerAzure Batchazure-batchazureworkerAzure Chaos Studioazure-chaos-studioazureworkerAzure Data Factoryazure-data-factoryazureworkerAzure Data Shareazure-data-shareazureworkerAzure Database Migration Serviceazure-database-migration-serviceazureworkerMicrosoft Entra Connect Syncazure-entra-connect-syncazureworkerMicrosoft Graph Data Connectazure-graph-data-connectazureworkerAzure Storage Moverazure-storage-moverazureworkerAzure Update Managerazure-update-managerazureworkerBrowser Runcloudflare-browser-runcloudflareworkerCloudflare Snippetscloudflare-snippetscloudflareworkerCloudflare Zarazcloudflare-zarazcloudflareworkerAirbyteairbyteworkerAirflow DAGairflow-dagworkerChaos Meshchaos-meshworkerChunkrchunkrworkerContainer workercontainer-workerworkerCron jobcron-jobworkerDaytonadaytonaworkerE2Be2bworkerEmbulkembulkworker
and 42 more → Worker page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Oracle Cloud Migrations: discovers VMware and EC2 assets through a remote agent appliance, plans
# the target shapes and replicates the workloads into OCI compute. "Oracle Cloud Migrations":
# a migration plan produces a Resource Manager stack that is deployed to launch the instances, so
# the migration runs when the plan is executed rather than on a schedule.
schemaVersion: "1"
type: "component"
id: "oci-cloud-migrations"
kind: "worker"
provider: "oci"
docs: "https://docs.oracle.com/en-us/iaas/Content/cloud-migration/home.htm"
defaults:
  managed: true
  trigger: "manual"
properties:
  sourceEnvironment:
    type: "enum"
    values: ["vmware", "aws-ec2"]
  remoteAgentAppliance:
    type: "boolean"
    default: true
  discoveryMethod:
    type: "enum"
    values: ["automated", "csv-import"]
    default: "automated"
  resourceManagerStack:
    type: "boolean"
    default: true
  replicationSchedule:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/oci-cloud-migrations.md