opentelekomcloud.SdrsReplicationAttachV1
Explore with Pulumi AI
Up-to-date reference of API arguments for SDRS replication pair attachment you can get at documentation portal
Manages a SDRS replication pair attachment resource within OpenTelekomCloud.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as opentelekomcloud from "@pulumi/opentelekomcloud";
const domain1 = opentelekomcloud.getSdrsDomainV1({});
const group1 = new opentelekomcloud.SdrsProtectiongroupV1("group1", {
sourceAvailabilityZone: "eu-de-02",
targetAvailabilityZone: "eu-de-01",
domainId: domain1.then(domain1 => domain1.id),
sourceVpcId: _var.vpc_id,
drType: "migration",
});
const instance1EcsInstanceV1 = new opentelekomcloud.EcsInstanceV1("instance1EcsInstanceV1", {
imageId: _var.image_id,
flavor: "s3.medium.1",
vpcId: _var.vpc_id,
nics: [{
networkId: _var.network_id,
}],
availabilityZone: "eu-de-02",
});
const instance1SdrsProtectedInstanceV1 = new opentelekomcloud.SdrsProtectedInstanceV1("instance1SdrsProtectedInstanceV1", {
groupId: group1.sdrsProtectiongroupV1Id,
serverId: instance1EcsInstanceV1.ecsInstanceV1Id,
deleteTargetServer: true,
});
const volume1 = new opentelekomcloud.EvsVolumeV3("volume1", {
description: "first test volume",
availabilityZone: "eu-de-02",
volumeType: "SATA",
size: 12,
});
const pair1 = new opentelekomcloud.SdrsReplicationPairV1("pair1", {
groupId: group1.sdrsProtectiongroupV1Id,
volumeId: volume1.evsVolumeV3Id,
deleteTargetVolume: true,
});
const attach1 = new opentelekomcloud.SdrsReplicationAttachV1("attach1", {
instanceId: instance1SdrsProtectedInstanceV1.sdrsProtectedInstanceV1Id,
replicationId: pair1.sdrsReplicationPairV1Id,
device: "/dev/vdb",
});
import pulumi
import pulumi_opentelekomcloud as opentelekomcloud
domain1 = opentelekomcloud.get_sdrs_domain_v1()
group1 = opentelekomcloud.SdrsProtectiongroupV1("group1",
source_availability_zone="eu-de-02",
target_availability_zone="eu-de-01",
domain_id=domain1.id,
source_vpc_id=var["vpc_id"],
dr_type="migration")
instance1_ecs_instance_v1 = opentelekomcloud.EcsInstanceV1("instance1EcsInstanceV1",
image_id=var["image_id"],
flavor="s3.medium.1",
vpc_id=var["vpc_id"],
nics=[{
"network_id": var["network_id"],
}],
availability_zone="eu-de-02")
instance1_sdrs_protected_instance_v1 = opentelekomcloud.SdrsProtectedInstanceV1("instance1SdrsProtectedInstanceV1",
group_id=group1.sdrs_protectiongroup_v1_id,
server_id=instance1_ecs_instance_v1.ecs_instance_v1_id,
delete_target_server=True)
volume1 = opentelekomcloud.EvsVolumeV3("volume1",
description="first test volume",
availability_zone="eu-de-02",
volume_type="SATA",
size=12)
pair1 = opentelekomcloud.SdrsReplicationPairV1("pair1",
group_id=group1.sdrs_protectiongroup_v1_id,
volume_id=volume1.evs_volume_v3_id,
delete_target_volume=True)
attach1 = opentelekomcloud.SdrsReplicationAttachV1("attach1",
instance_id=instance1_sdrs_protected_instance_v1.sdrs_protected_instance_v1_id,
replication_id=pair1.sdrs_replication_pair_v1_id,
device="/dev/vdb")
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/opentelekomcloud/opentelekomcloud"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
domain1, err := opentelekomcloud.GetSdrsDomainV1(ctx, &opentelekomcloud.GetSdrsDomainV1Args{}, nil)
if err != nil {
return err
}
group1, err := opentelekomcloud.NewSdrsProtectiongroupV1(ctx, "group1", &opentelekomcloud.SdrsProtectiongroupV1Args{
SourceAvailabilityZone: pulumi.String("eu-de-02"),
TargetAvailabilityZone: pulumi.String("eu-de-01"),
DomainId: pulumi.String(domain1.Id),
SourceVpcId: pulumi.Any(_var.Vpc_id),
DrType: pulumi.String("migration"),
})
if err != nil {
return err
}
instance1EcsInstanceV1, err := opentelekomcloud.NewEcsInstanceV1(ctx, "instance1EcsInstanceV1", &opentelekomcloud.EcsInstanceV1Args{
ImageId: pulumi.Any(_var.Image_id),
Flavor: pulumi.String("s3.medium.1"),
VpcId: pulumi.Any(_var.Vpc_id),
Nics: opentelekomcloud.EcsInstanceV1NicArray{
&opentelekomcloud.EcsInstanceV1NicArgs{
NetworkId: pulumi.Any(_var.Network_id),
},
},
AvailabilityZone: pulumi.String("eu-de-02"),
})
if err != nil {
return err
}
instance1SdrsProtectedInstanceV1, err := opentelekomcloud.NewSdrsProtectedInstanceV1(ctx, "instance1SdrsProtectedInstanceV1", &opentelekomcloud.SdrsProtectedInstanceV1Args{
GroupId: group1.SdrsProtectiongroupV1Id,
ServerId: instance1EcsInstanceV1.EcsInstanceV1Id,
DeleteTargetServer: pulumi.Bool(true),
})
if err != nil {
return err
}
volume1, err := opentelekomcloud.NewEvsVolumeV3(ctx, "volume1", &opentelekomcloud.EvsVolumeV3Args{
Description: pulumi.String("first test volume"),
AvailabilityZone: pulumi.String("eu-de-02"),
VolumeType: pulumi.String("SATA"),
Size: pulumi.Float64(12),
})
if err != nil {
return err
}
pair1, err := opentelekomcloud.NewSdrsReplicationPairV1(ctx, "pair1", &opentelekomcloud.SdrsReplicationPairV1Args{
GroupId: group1.SdrsProtectiongroupV1Id,
VolumeId: volume1.EvsVolumeV3Id,
DeleteTargetVolume: pulumi.Bool(true),
})
if err != nil {
return err
}
_, err = opentelekomcloud.NewSdrsReplicationAttachV1(ctx, "attach1", &opentelekomcloud.SdrsReplicationAttachV1Args{
InstanceId: instance1SdrsProtectedInstanceV1.SdrsProtectedInstanceV1Id,
ReplicationId: pair1.SdrsReplicationPairV1Id,
Device: pulumi.String("/dev/vdb"),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Opentelekomcloud = Pulumi.Opentelekomcloud;
return await Deployment.RunAsync(() =>
{
var domain1 = Opentelekomcloud.GetSdrsDomainV1.Invoke();
var group1 = new Opentelekomcloud.SdrsProtectiongroupV1("group1", new()
{
SourceAvailabilityZone = "eu-de-02",
TargetAvailabilityZone = "eu-de-01",
DomainId = domain1.Apply(getSdrsDomainV1Result => getSdrsDomainV1Result.Id),
SourceVpcId = @var.Vpc_id,
DrType = "migration",
});
var instance1EcsInstanceV1 = new Opentelekomcloud.EcsInstanceV1("instance1EcsInstanceV1", new()
{
ImageId = @var.Image_id,
Flavor = "s3.medium.1",
VpcId = @var.Vpc_id,
Nics = new[]
{
new Opentelekomcloud.Inputs.EcsInstanceV1NicArgs
{
NetworkId = @var.Network_id,
},
},
AvailabilityZone = "eu-de-02",
});
var instance1SdrsProtectedInstanceV1 = new Opentelekomcloud.SdrsProtectedInstanceV1("instance1SdrsProtectedInstanceV1", new()
{
GroupId = group1.SdrsProtectiongroupV1Id,
ServerId = instance1EcsInstanceV1.EcsInstanceV1Id,
DeleteTargetServer = true,
});
var volume1 = new Opentelekomcloud.EvsVolumeV3("volume1", new()
{
Description = "first test volume",
AvailabilityZone = "eu-de-02",
VolumeType = "SATA",
Size = 12,
});
var pair1 = new Opentelekomcloud.SdrsReplicationPairV1("pair1", new()
{
GroupId = group1.SdrsProtectiongroupV1Id,
VolumeId = volume1.EvsVolumeV3Id,
DeleteTargetVolume = true,
});
var attach1 = new Opentelekomcloud.SdrsReplicationAttachV1("attach1", new()
{
InstanceId = instance1SdrsProtectedInstanceV1.SdrsProtectedInstanceV1Id,
ReplicationId = pair1.SdrsReplicationPairV1Id,
Device = "/dev/vdb",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.opentelekomcloud.OpentelekomcloudFunctions;
import com.pulumi.opentelekomcloud.inputs.GetSdrsDomainV1Args;
import com.pulumi.opentelekomcloud.SdrsProtectiongroupV1;
import com.pulumi.opentelekomcloud.SdrsProtectiongroupV1Args;
import com.pulumi.opentelekomcloud.EcsInstanceV1;
import com.pulumi.opentelekomcloud.EcsInstanceV1Args;
import com.pulumi.opentelekomcloud.inputs.EcsInstanceV1NicArgs;
import com.pulumi.opentelekomcloud.SdrsProtectedInstanceV1;
import com.pulumi.opentelekomcloud.SdrsProtectedInstanceV1Args;
import com.pulumi.opentelekomcloud.EvsVolumeV3;
import com.pulumi.opentelekomcloud.EvsVolumeV3Args;
import com.pulumi.opentelekomcloud.SdrsReplicationPairV1;
import com.pulumi.opentelekomcloud.SdrsReplicationPairV1Args;
import com.pulumi.opentelekomcloud.SdrsReplicationAttachV1;
import com.pulumi.opentelekomcloud.SdrsReplicationAttachV1Args;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var domain1 = OpentelekomcloudFunctions.getSdrsDomainV1();
var group1 = new SdrsProtectiongroupV1("group1", SdrsProtectiongroupV1Args.builder()
.sourceAvailabilityZone("eu-de-02")
.targetAvailabilityZone("eu-de-01")
.domainId(domain1.applyValue(getSdrsDomainV1Result -> getSdrsDomainV1Result.id()))
.sourceVpcId(var_.vpc_id())
.drType("migration")
.build());
var instance1EcsInstanceV1 = new EcsInstanceV1("instance1EcsInstanceV1", EcsInstanceV1Args.builder()
.imageId(var_.image_id())
.flavor("s3.medium.1")
.vpcId(var_.vpc_id())
.nics(EcsInstanceV1NicArgs.builder()
.networkId(var_.network_id())
.build())
.availabilityZone("eu-de-02")
.build());
var instance1SdrsProtectedInstanceV1 = new SdrsProtectedInstanceV1("instance1SdrsProtectedInstanceV1", SdrsProtectedInstanceV1Args.builder()
.groupId(group1.sdrsProtectiongroupV1Id())
.serverId(instance1EcsInstanceV1.ecsInstanceV1Id())
.deleteTargetServer(true)
.build());
var volume1 = new EvsVolumeV3("volume1", EvsVolumeV3Args.builder()
.description("first test volume")
.availabilityZone("eu-de-02")
.volumeType("SATA")
.size(12)
.build());
var pair1 = new SdrsReplicationPairV1("pair1", SdrsReplicationPairV1Args.builder()
.groupId(group1.sdrsProtectiongroupV1Id())
.volumeId(volume1.evsVolumeV3Id())
.deleteTargetVolume(true)
.build());
var attach1 = new SdrsReplicationAttachV1("attach1", SdrsReplicationAttachV1Args.builder()
.instanceId(instance1SdrsProtectedInstanceV1.sdrsProtectedInstanceV1Id())
.replicationId(pair1.sdrsReplicationPairV1Id())
.device("/dev/vdb")
.build());
}
}
resources:
group1:
type: opentelekomcloud:SdrsProtectiongroupV1
properties:
sourceAvailabilityZone: eu-de-02
targetAvailabilityZone: eu-de-01
domainId: ${domain1.id}
sourceVpcId: ${var.vpc_id}
drType: migration
instance1EcsInstanceV1:
type: opentelekomcloud:EcsInstanceV1
properties:
imageId: ${var.image_id}
flavor: s3.medium.1
vpcId: ${var.vpc_id}
nics:
- networkId: ${var.network_id}
availabilityZone: eu-de-02
instance1SdrsProtectedInstanceV1:
type: opentelekomcloud:SdrsProtectedInstanceV1
properties:
groupId: ${group1.sdrsProtectiongroupV1Id}
serverId: ${instance1EcsInstanceV1.ecsInstanceV1Id}
deleteTargetServer: true
volume1:
type: opentelekomcloud:EvsVolumeV3
properties:
description: first test volume
availabilityZone: eu-de-02
volumeType: SATA
size: 12
pair1:
type: opentelekomcloud:SdrsReplicationPairV1
properties:
groupId: ${group1.sdrsProtectiongroupV1Id}
volumeId: ${volume1.evsVolumeV3Id}
deleteTargetVolume: true
attach1:
type: opentelekomcloud:SdrsReplicationAttachV1
properties:
instanceId: ${instance1SdrsProtectedInstanceV1.sdrsProtectedInstanceV1Id}
replicationId: ${pair1.sdrsReplicationPairV1Id}
device: /dev/vdb
variables:
domain1:
fn::invoke:
function: opentelekomcloud:getSdrsDomainV1
arguments: {}
Create SdrsReplicationAttachV1 Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new SdrsReplicationAttachV1(name: string, args: SdrsReplicationAttachV1Args, opts?: CustomResourceOptions);
@overload
def SdrsReplicationAttachV1(resource_name: str,
args: SdrsReplicationAttachV1Args,
opts: Optional[ResourceOptions] = None)
@overload
def SdrsReplicationAttachV1(resource_name: str,
opts: Optional[ResourceOptions] = None,
device: Optional[str] = None,
instance_id: Optional[str] = None,
replication_id: Optional[str] = None,
sdrs_replication_attach_v1_id: Optional[str] = None,
timeouts: Optional[SdrsReplicationAttachV1TimeoutsArgs] = None)
func NewSdrsReplicationAttachV1(ctx *Context, name string, args SdrsReplicationAttachV1Args, opts ...ResourceOption) (*SdrsReplicationAttachV1, error)
public SdrsReplicationAttachV1(string name, SdrsReplicationAttachV1Args args, CustomResourceOptions? opts = null)
public SdrsReplicationAttachV1(String name, SdrsReplicationAttachV1Args args)
public SdrsReplicationAttachV1(String name, SdrsReplicationAttachV1Args args, CustomResourceOptions options)
type: opentelekomcloud:SdrsReplicationAttachV1
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args SdrsReplicationAttachV1Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args SdrsReplicationAttachV1Args
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args SdrsReplicationAttachV1Args
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args SdrsReplicationAttachV1Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args SdrsReplicationAttachV1Args
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var sdrsReplicationAttachV1Resource = new Opentelekomcloud.SdrsReplicationAttachV1("sdrsReplicationAttachV1Resource", new()
{
Device = "string",
InstanceId = "string",
ReplicationId = "string",
SdrsReplicationAttachV1Id = "string",
Timeouts = new Opentelekomcloud.Inputs.SdrsReplicationAttachV1TimeoutsArgs
{
Create = "string",
Delete = "string",
},
});
example, err := opentelekomcloud.NewSdrsReplicationAttachV1(ctx, "sdrsReplicationAttachV1Resource", &opentelekomcloud.SdrsReplicationAttachV1Args{
Device: pulumi.String("string"),
InstanceId: pulumi.String("string"),
ReplicationId: pulumi.String("string"),
SdrsReplicationAttachV1Id: pulumi.String("string"),
Timeouts: &opentelekomcloud.SdrsReplicationAttachV1TimeoutsArgs{
Create: pulumi.String("string"),
Delete: pulumi.String("string"),
},
})
var sdrsReplicationAttachV1Resource = new SdrsReplicationAttachV1("sdrsReplicationAttachV1Resource", SdrsReplicationAttachV1Args.builder()
.device("string")
.instanceId("string")
.replicationId("string")
.sdrsReplicationAttachV1Id("string")
.timeouts(SdrsReplicationAttachV1TimeoutsArgs.builder()
.create("string")
.delete("string")
.build())
.build());
sdrs_replication_attach_v1_resource = opentelekomcloud.SdrsReplicationAttachV1("sdrsReplicationAttachV1Resource",
device="string",
instance_id="string",
replication_id="string",
sdrs_replication_attach_v1_id="string",
timeouts={
"create": "string",
"delete": "string",
})
const sdrsReplicationAttachV1Resource = new opentelekomcloud.SdrsReplicationAttachV1("sdrsReplicationAttachV1Resource", {
device: "string",
instanceId: "string",
replicationId: "string",
sdrsReplicationAttachV1Id: "string",
timeouts: {
create: "string",
"delete": "string",
},
});
type: opentelekomcloud:SdrsReplicationAttachV1
properties:
device: string
instanceId: string
replicationId: string
sdrsReplicationAttachV1Id: string
timeouts:
create: string
delete: string
SdrsReplicationAttachV1 Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The SdrsReplicationAttachV1 resource accepts the following input properties:
- Device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- Instance
Id string - Specifies the ID of a protected instance.
- Replication
Id string - Specifies the ID of a replication pair.
- Sdrs
Replication stringAttach V1Id - The resource ID.
- Timeouts
Sdrs
Replication Attach V1Timeouts
- Device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- Instance
Id string - Specifies the ID of a protected instance.
- Replication
Id string - Specifies the ID of a replication pair.
- Sdrs
Replication stringAttach V1Id - The resource ID.
- Timeouts
Sdrs
Replication Attach V1Timeouts Args
- device String
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id String - Specifies the ID of a protected instance.
- replication
Id String - Specifies the ID of a replication pair.
- sdrs
Replication StringAttach V1Id - The resource ID.
- timeouts
Sdrs
Replication Attach V1Timeouts
- device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id string - Specifies the ID of a protected instance.
- replication
Id string - Specifies the ID of a replication pair.
- sdrs
Replication stringAttach V1Id - The resource ID.
- timeouts
Sdrs
Replication Attach V1Timeouts
- device str
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance_
id str - Specifies the ID of a protected instance.
- replication_
id str - Specifies the ID of a replication pair.
- sdrs_
replication_ strattach_ v1_ id - The resource ID.
- timeouts
Sdrs
Replication Attach V1Timeouts Args
- device String
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id String - Specifies the ID of a protected instance.
- replication
Id String - Specifies the ID of a replication pair.
- sdrs
Replication StringAttach V1Id - The resource ID.
- timeouts Property Map
Outputs
All input properties are implicitly available as output properties. Additionally, the SdrsReplicationAttachV1 resource produces the following output properties:
Look up Existing SdrsReplicationAttachV1 Resource
Get an existing SdrsReplicationAttachV1 resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: SdrsReplicationAttachV1State, opts?: CustomResourceOptions): SdrsReplicationAttachV1
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
device: Optional[str] = None,
instance_id: Optional[str] = None,
region: Optional[str] = None,
replication_id: Optional[str] = None,
sdrs_replication_attach_v1_id: Optional[str] = None,
status: Optional[str] = None,
timeouts: Optional[SdrsReplicationAttachV1TimeoutsArgs] = None) -> SdrsReplicationAttachV1
func GetSdrsReplicationAttachV1(ctx *Context, name string, id IDInput, state *SdrsReplicationAttachV1State, opts ...ResourceOption) (*SdrsReplicationAttachV1, error)
public static SdrsReplicationAttachV1 Get(string name, Input<string> id, SdrsReplicationAttachV1State? state, CustomResourceOptions? opts = null)
public static SdrsReplicationAttachV1 get(String name, Output<String> id, SdrsReplicationAttachV1State state, CustomResourceOptions options)
resources: _: type: opentelekomcloud:SdrsReplicationAttachV1 get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- Instance
Id string - Specifies the ID of a protected instance.
- Region string
- The attachment region.
- Replication
Id string - Specifies the ID of a replication pair.
- Sdrs
Replication stringAttach V1Id - The resource ID.
- Status string
- The status of the SDRS protected instance.
- Timeouts
Sdrs
Replication Attach V1Timeouts
- Device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- Instance
Id string - Specifies the ID of a protected instance.
- Region string
- The attachment region.
- Replication
Id string - Specifies the ID of a replication pair.
- Sdrs
Replication stringAttach V1Id - The resource ID.
- Status string
- The status of the SDRS protected instance.
- Timeouts
Sdrs
Replication Attach V1Timeouts Args
- device String
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id String - Specifies the ID of a protected instance.
- region String
- The attachment region.
- replication
Id String - Specifies the ID of a replication pair.
- sdrs
Replication StringAttach V1Id - The resource ID.
- status String
- The status of the SDRS protected instance.
- timeouts
Sdrs
Replication Attach V1Timeouts
- device string
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id string - Specifies the ID of a protected instance.
- region string
- The attachment region.
- replication
Id string - Specifies the ID of a replication pair.
- sdrs
Replication stringAttach V1Id - The resource ID.
- status string
- The status of the SDRS protected instance.
- timeouts
Sdrs
Replication Attach V1Timeouts
- device str
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance_
id str - Specifies the ID of a protected instance.
- region str
- The attachment region.
- replication_
id str - Specifies the ID of a replication pair.
- sdrs_
replication_ strattach_ v1_ id - The resource ID.
- status str
- The status of the SDRS protected instance.
- timeouts
Sdrs
Replication Attach V1Timeouts Args
- device String
Specifies the disk device name of a replication pair. There are several restrictions on this field as follows:
The new disk device name cannot be the same as an existing one.
Set the parameter value to /dev/sda for the system disks of protected instances created using Xen servers and to /dev/sdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/sdb and /dev/sdc, respectively. If you set a device name starting with /dev/vd, the system uses /dev/sd by default.
Set the parameter value to /dev/vda for the system disks of protected instances created using KVM servers and to /dev/vdx for data disks, where x is a letter in alphabetical order. For example, if there are two data disks, set the device names of the two data disks to /dev/vdb and /dev/vdc, respectively. If you set a device name starting with /dev/sd, the system uses /dev/vd by default.
- instance
Id String - Specifies the ID of a protected instance.
- region String
- The attachment region.
- replication
Id String - Specifies the ID of a replication pair.
- sdrs
Replication StringAttach V1Id - The resource ID.
- status String
- The status of the SDRS protected instance.
- timeouts Property Map
Supporting Types
SdrsReplicationAttachV1Timeouts, SdrsReplicationAttachV1TimeoutsArgs
Import
The SDRS replication attach can be imported using the protected_instance_id
and replication_id
, separated
by a slash , e.g.
bash
$ pulumi import opentelekomcloud:index/sdrsReplicationAttachV1:SdrsReplicationAttachV1 test <protected_instance_id>/<replication_id>
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- opentelekomcloud opentelekomcloud/terraform-provider-opentelekomcloud
- License
- Notes
- This Pulumi package is based on the
opentelekomcloud
Terraform Provider.