diff options
author | CoprDistGit <infra@openeuler.org> | 2023-04-11 05:33:50 +0000 |
---|---|---|
committer | CoprDistGit <infra@openeuler.org> | 2023-04-11 05:33:50 +0000 |
commit | 4087a52f899b18ff24b6c7b07273f412c1c9ff3f (patch) | |
tree | 08c26fc389dcc242019fd73846186b1ba593c225 | |
parent | e70d99a013e31198479a67d19d1dcb00c024e7a4 (diff) |
automatic import of python-cdk-spot-one
-rw-r--r-- | .gitignore | 1 | ||||
-rw-r--r-- | python-cdk-spot-one.spec | 572 | ||||
-rw-r--r-- | sources | 1 |
3 files changed, 574 insertions, 0 deletions
@@ -0,0 +1 @@ +/cdk-spot-one-2.0.328.tar.gz diff --git a/python-cdk-spot-one.spec b/python-cdk-spot-one.spec new file mode 100644 index 0000000..74c3fb4 --- /dev/null +++ b/python-cdk-spot-one.spec @@ -0,0 +1,572 @@ +%global _empty_manifest_terminate_build 0 +Name: python-cdk-spot-one +Version: 2.0.328 +Release: 1 +Summary: One spot instance with EIP and defined duration. No interruption. +License: Apache-2.0 +URL: https://github.com/pahud/cdk-spot-one.git +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3a/f0/bcd0f1f43e4a29ad96a271b3beefb8ba64e0cbb1f19ac9397009553ce687/cdk-spot-one-2.0.328.tar.gz +BuildArch: noarch + +Requires: python3-aws-cdk-lib +Requires: python3-constructs +Requires: python3-jsii +Requires: python3-publication +Requires: python3-typeguard + +%description +[](https://badge.fury.io/js/cdk-spot-one) +[](https://badge.fury.io/py/cdk-spot-one) + + +# cdk-spot-one + +One spot instance with EIP and defined duration. No interruption. + +# Install + +Use the npm dist tag to opt in CDKv1 or CDKv2: + +```sh +// for CDKv2 +npm install cdk-spot-one +or +npm install cdk-spot-one@latest + +// for CDKv1 +npm install cdk-spot-one@cdkv1 +``` + +# Why + +Sometimes we need an Amazon EC2 instance with static fixed IP for testing or development purpose for a duration of +time(probably hours). We need to make sure during this time, no interruption will occur and we don't want to pay +for on-demand rate. `cdk-spot-one` helps you reserve one single spot instance with pre-allocated or new +Elastic IP addresses(EIP) with defined `blockDuration`, during which time the spot instance will be secured with no spot interruption. + +Behind the scene, `cdk-spot-one` provisions a spot fleet with capacity of single instance for you and it associates the EIP with this instance. The spot fleet is reserved as spot block with `blockDuration` from one hour up to six hours to ensure the high availability for your spot instance. + +Multiple spot instances are possible by simply specifying the `targetCapacity` construct property, but we only associate the EIP with the first spot instance at this moment. + +Enjoy your highly durable one spot instance with AWS CDK! + +# Constructs + +This library provides two major constructs: + +## SpotInstance + +* Create a spot instance **without** any fleet +* Does **NOT** support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Support `stop` or `hibernate` instance + +Scenario: To leverage the `stop` or `hibernate` capabilities of the spot instance to persist the data in the ebs volume. + +## SpotFleet + +* Create a spot instance with a [Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html) +* Support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Does **NOT** support `stop` or `hibernate` instance + +Scenario: To ensure the availability with no disruption with defined period up to 6 hours. + +# Sample + +## SpotInstance + +```python +import { SpotInstance, AmazonMachineImage } from 'cdk-spot-one'; + +// Default use Amazon Linux 2 +new SpotInstance(stack, 'SpotInstance'); + + +// Custom Id use Ubuntu 20.04 Arm64 Server. +new SpotInstance(stack, 'SpotInstanceUbuntu', { + vpc, + customAmiId: AmazonMachineImage.UBUNTU_20_04_ARM64.getImage(stack).imageId, + defaultInstanceType: new InstanceType('t4g.medium'), + keyName, + blockDeviceMappings: [{ deviceName: '/dev/sda1', ebs: { volumeSize: 20 } }], + additionalUserData: ['curl -fsSL https://get.docker.com -o get-docker.sh', 'sudo sh get-docker.sh'], + }); +``` + +## SpotFleet + +```python +import { SpotFleet } from 'cdk-spot-one'; + +// create the first fleet for one hour and associate with our existing EIP +const fleet = new SpotFleet(stack, 'SpotFleet') + +// configure the expiration after 1 hour +fleet.expireAfter(Duration.hours(1)) + + +// create the 2nd fleet with single Gravition 2 instance for 6 hours and associate with new EIP +const fleet2 = new SpotFleet(stack, 'SpotFleet2', { + blockDuration: BlockDuration.SIX_HOURS, + eipAllocationId: 'eipalloc-0d1bc6d85895a5410', + defaultInstanceType: new InstanceType('c6g.large'), + vpc: fleet.vpc, +}) +// configure the expiration after 6 hours +fleet2.expireAfter(Duration.hours(6)) + +// print the instanceId from each spot fleet +new CfnOutput(stack, 'SpotFleetInstanceId', { value: fleet.instanceId }) +new CfnOutput(stack, 'SpotFleet2InstanceId', { value: fleet2.instanceId }) +``` + +# Create spot instances without duration block + +```python +const fleet = new SpotFleet(stack, 'SpotFleet', { + blockDuration: BlockDuration.NONE, +}) +``` + +NOTE: This kind of spot instance will be interrupted by AWS. However the fleet is using type [maintain](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html#spot-fleet-allocation-strategy), the fleet can be refulfilled. + +# ARM64 and Graviton 2 support + +`cdk-spot-one` selects the latest Amazon Linux 2 AMI for your `ARM64` instances. Simply select the instance types with the `defaultInstanceType` property and the `SpotFleet` will auto configure correct AMI for the instance. + +```python +defaultInstanceType: new InstanceType('c6g.large') +``` + +# ECS Cluster support + +See https://github.com/pahud/cdk-spot-one/issues/270#issuecomment-877152685 + +# Connect with Session Manager(recommended) + +You may connect to the spot instance with [Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-sessions-start.html). + +```sh +# make sure you have installed session-manager-plugin +$ session-manager-plugin +# start session +$ aws ssm start-session --target INSTANCE_ID +``` + +# Connect with EC2 SSH Connect + +By default the `cdk-spot-one` does not bind any SSH public key for you on the instance. You are encouraged to use `ec2-instance-connect` to send your public key from local followed by one-time SSH connect. + +For example: + +```sh +pubkey="$HOME/.ssh/aws_2020_id_rsa.pub" +echo "sending public key to ${instanceId}" +aws ec2-instance-connect send-ssh-public-key --instance-id ${instanceId} --instance-os-user ec2-user \ +--ssh-public-key file://${pubkey} --availability-zone ${az} +``` + +## npx ec2-connect INSTANCE_ID + +To connect to the instance, run `npx ec2-connect` as below: + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 +``` + +or + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 ~/.ssh/other_public_key_path +``` + +If you are using different SSH public key(default is ~/.ssh/id_rsa.pub) + + +%package -n python3-cdk-spot-one +Summary: One spot instance with EIP and defined duration. No interruption. +Provides: python-cdk-spot-one +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-cdk-spot-one +[](https://badge.fury.io/js/cdk-spot-one) +[](https://badge.fury.io/py/cdk-spot-one) + + +# cdk-spot-one + +One spot instance with EIP and defined duration. No interruption. + +# Install + +Use the npm dist tag to opt in CDKv1 or CDKv2: + +```sh +// for CDKv2 +npm install cdk-spot-one +or +npm install cdk-spot-one@latest + +// for CDKv1 +npm install cdk-spot-one@cdkv1 +``` + +# Why + +Sometimes we need an Amazon EC2 instance with static fixed IP for testing or development purpose for a duration of +time(probably hours). We need to make sure during this time, no interruption will occur and we don't want to pay +for on-demand rate. `cdk-spot-one` helps you reserve one single spot instance with pre-allocated or new +Elastic IP addresses(EIP) with defined `blockDuration`, during which time the spot instance will be secured with no spot interruption. + +Behind the scene, `cdk-spot-one` provisions a spot fleet with capacity of single instance for you and it associates the EIP with this instance. The spot fleet is reserved as spot block with `blockDuration` from one hour up to six hours to ensure the high availability for your spot instance. + +Multiple spot instances are possible by simply specifying the `targetCapacity` construct property, but we only associate the EIP with the first spot instance at this moment. + +Enjoy your highly durable one spot instance with AWS CDK! + +# Constructs + +This library provides two major constructs: + +## SpotInstance + +* Create a spot instance **without** any fleet +* Does **NOT** support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Support `stop` or `hibernate` instance + +Scenario: To leverage the `stop` or `hibernate` capabilities of the spot instance to persist the data in the ebs volume. + +## SpotFleet + +* Create a spot instance with a [Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html) +* Support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Does **NOT** support `stop` or `hibernate` instance + +Scenario: To ensure the availability with no disruption with defined period up to 6 hours. + +# Sample + +## SpotInstance + +```python +import { SpotInstance, AmazonMachineImage } from 'cdk-spot-one'; + +// Default use Amazon Linux 2 +new SpotInstance(stack, 'SpotInstance'); + + +// Custom Id use Ubuntu 20.04 Arm64 Server. +new SpotInstance(stack, 'SpotInstanceUbuntu', { + vpc, + customAmiId: AmazonMachineImage.UBUNTU_20_04_ARM64.getImage(stack).imageId, + defaultInstanceType: new InstanceType('t4g.medium'), + keyName, + blockDeviceMappings: [{ deviceName: '/dev/sda1', ebs: { volumeSize: 20 } }], + additionalUserData: ['curl -fsSL https://get.docker.com -o get-docker.sh', 'sudo sh get-docker.sh'], + }); +``` + +## SpotFleet + +```python +import { SpotFleet } from 'cdk-spot-one'; + +// create the first fleet for one hour and associate with our existing EIP +const fleet = new SpotFleet(stack, 'SpotFleet') + +// configure the expiration after 1 hour +fleet.expireAfter(Duration.hours(1)) + + +// create the 2nd fleet with single Gravition 2 instance for 6 hours and associate with new EIP +const fleet2 = new SpotFleet(stack, 'SpotFleet2', { + blockDuration: BlockDuration.SIX_HOURS, + eipAllocationId: 'eipalloc-0d1bc6d85895a5410', + defaultInstanceType: new InstanceType('c6g.large'), + vpc: fleet.vpc, +}) +// configure the expiration after 6 hours +fleet2.expireAfter(Duration.hours(6)) + +// print the instanceId from each spot fleet +new CfnOutput(stack, 'SpotFleetInstanceId', { value: fleet.instanceId }) +new CfnOutput(stack, 'SpotFleet2InstanceId', { value: fleet2.instanceId }) +``` + +# Create spot instances without duration block + +```python +const fleet = new SpotFleet(stack, 'SpotFleet', { + blockDuration: BlockDuration.NONE, +}) +``` + +NOTE: This kind of spot instance will be interrupted by AWS. However the fleet is using type [maintain](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html#spot-fleet-allocation-strategy), the fleet can be refulfilled. + +# ARM64 and Graviton 2 support + +`cdk-spot-one` selects the latest Amazon Linux 2 AMI for your `ARM64` instances. Simply select the instance types with the `defaultInstanceType` property and the `SpotFleet` will auto configure correct AMI for the instance. + +```python +defaultInstanceType: new InstanceType('c6g.large') +``` + +# ECS Cluster support + +See https://github.com/pahud/cdk-spot-one/issues/270#issuecomment-877152685 + +# Connect with Session Manager(recommended) + +You may connect to the spot instance with [Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-sessions-start.html). + +```sh +# make sure you have installed session-manager-plugin +$ session-manager-plugin +# start session +$ aws ssm start-session --target INSTANCE_ID +``` + +# Connect with EC2 SSH Connect + +By default the `cdk-spot-one` does not bind any SSH public key for you on the instance. You are encouraged to use `ec2-instance-connect` to send your public key from local followed by one-time SSH connect. + +For example: + +```sh +pubkey="$HOME/.ssh/aws_2020_id_rsa.pub" +echo "sending public key to ${instanceId}" +aws ec2-instance-connect send-ssh-public-key --instance-id ${instanceId} --instance-os-user ec2-user \ +--ssh-public-key file://${pubkey} --availability-zone ${az} +``` + +## npx ec2-connect INSTANCE_ID + +To connect to the instance, run `npx ec2-connect` as below: + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 +``` + +or + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 ~/.ssh/other_public_key_path +``` + +If you are using different SSH public key(default is ~/.ssh/id_rsa.pub) + + +%package help +Summary: Development documents and examples for cdk-spot-one +Provides: python3-cdk-spot-one-doc +%description help +[](https://badge.fury.io/js/cdk-spot-one) +[](https://badge.fury.io/py/cdk-spot-one) + + +# cdk-spot-one + +One spot instance with EIP and defined duration. No interruption. + +# Install + +Use the npm dist tag to opt in CDKv1 or CDKv2: + +```sh +// for CDKv2 +npm install cdk-spot-one +or +npm install cdk-spot-one@latest + +// for CDKv1 +npm install cdk-spot-one@cdkv1 +``` + +# Why + +Sometimes we need an Amazon EC2 instance with static fixed IP for testing or development purpose for a duration of +time(probably hours). We need to make sure during this time, no interruption will occur and we don't want to pay +for on-demand rate. `cdk-spot-one` helps you reserve one single spot instance with pre-allocated or new +Elastic IP addresses(EIP) with defined `blockDuration`, during which time the spot instance will be secured with no spot interruption. + +Behind the scene, `cdk-spot-one` provisions a spot fleet with capacity of single instance for you and it associates the EIP with this instance. The spot fleet is reserved as spot block with `blockDuration` from one hour up to six hours to ensure the high availability for your spot instance. + +Multiple spot instances are possible by simply specifying the `targetCapacity` construct property, but we only associate the EIP with the first spot instance at this moment. + +Enjoy your highly durable one spot instance with AWS CDK! + +# Constructs + +This library provides two major constructs: + +## SpotInstance + +* Create a spot instance **without** any fleet +* Does **NOT** support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Support `stop` or `hibernate` instance + +Scenario: To leverage the `stop` or `hibernate` capabilities of the spot instance to persist the data in the ebs volume. + +## SpotFleet + +* Create a spot instance with a [Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html) +* Support [Spot Block](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#fixed-duration-spot-instances) +* Does **NOT** support `stop` or `hibernate` instance + +Scenario: To ensure the availability with no disruption with defined period up to 6 hours. + +# Sample + +## SpotInstance + +```python +import { SpotInstance, AmazonMachineImage } from 'cdk-spot-one'; + +// Default use Amazon Linux 2 +new SpotInstance(stack, 'SpotInstance'); + + +// Custom Id use Ubuntu 20.04 Arm64 Server. +new SpotInstance(stack, 'SpotInstanceUbuntu', { + vpc, + customAmiId: AmazonMachineImage.UBUNTU_20_04_ARM64.getImage(stack).imageId, + defaultInstanceType: new InstanceType('t4g.medium'), + keyName, + blockDeviceMappings: [{ deviceName: '/dev/sda1', ebs: { volumeSize: 20 } }], + additionalUserData: ['curl -fsSL https://get.docker.com -o get-docker.sh', 'sudo sh get-docker.sh'], + }); +``` + +## SpotFleet + +```python +import { SpotFleet } from 'cdk-spot-one'; + +// create the first fleet for one hour and associate with our existing EIP +const fleet = new SpotFleet(stack, 'SpotFleet') + +// configure the expiration after 1 hour +fleet.expireAfter(Duration.hours(1)) + + +// create the 2nd fleet with single Gravition 2 instance for 6 hours and associate with new EIP +const fleet2 = new SpotFleet(stack, 'SpotFleet2', { + blockDuration: BlockDuration.SIX_HOURS, + eipAllocationId: 'eipalloc-0d1bc6d85895a5410', + defaultInstanceType: new InstanceType('c6g.large'), + vpc: fleet.vpc, +}) +// configure the expiration after 6 hours +fleet2.expireAfter(Duration.hours(6)) + +// print the instanceId from each spot fleet +new CfnOutput(stack, 'SpotFleetInstanceId', { value: fleet.instanceId }) +new CfnOutput(stack, 'SpotFleet2InstanceId', { value: fleet2.instanceId }) +``` + +# Create spot instances without duration block + +```python +const fleet = new SpotFleet(stack, 'SpotFleet', { + blockDuration: BlockDuration.NONE, +}) +``` + +NOTE: This kind of spot instance will be interrupted by AWS. However the fleet is using type [maintain](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html#spot-fleet-allocation-strategy), the fleet can be refulfilled. + +# ARM64 and Graviton 2 support + +`cdk-spot-one` selects the latest Amazon Linux 2 AMI for your `ARM64` instances. Simply select the instance types with the `defaultInstanceType` property and the `SpotFleet` will auto configure correct AMI for the instance. + +```python +defaultInstanceType: new InstanceType('c6g.large') +``` + +# ECS Cluster support + +See https://github.com/pahud/cdk-spot-one/issues/270#issuecomment-877152685 + +# Connect with Session Manager(recommended) + +You may connect to the spot instance with [Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-sessions-start.html). + +```sh +# make sure you have installed session-manager-plugin +$ session-manager-plugin +# start session +$ aws ssm start-session --target INSTANCE_ID +``` + +# Connect with EC2 SSH Connect + +By default the `cdk-spot-one` does not bind any SSH public key for you on the instance. You are encouraged to use `ec2-instance-connect` to send your public key from local followed by one-time SSH connect. + +For example: + +```sh +pubkey="$HOME/.ssh/aws_2020_id_rsa.pub" +echo "sending public key to ${instanceId}" +aws ec2-instance-connect send-ssh-public-key --instance-id ${instanceId} --instance-os-user ec2-user \ +--ssh-public-key file://${pubkey} --availability-zone ${az} +``` + +## npx ec2-connect INSTANCE_ID + +To connect to the instance, run `npx ec2-connect` as below: + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 +``` + +or + +```sh +$ npx ec2-connect i-01f827ab9de7b93a9 ~/.ssh/other_public_key_path +``` + +If you are using different SSH public key(default is ~/.ssh/id_rsa.pub) + + +%prep +%autosetup -n cdk-spot-one-2.0.328 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-cdk-spot-one -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.0.328-1 +- Package Spec generated @@ -0,0 +1 @@ +c6fa64fd39730dd0de141373ce6ace4e cdk-spot-one-2.0.328.tar.gz |