-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand the Amazon AWS ec2 integration and add content for Amazon elb and s3. #522
Comments
I have an issue regarding implementation of Create Server that is need to be discussed. |
The priorities are: EC2 - Images and EC2 - Load balancers, after that S3 |
According with AGM now the top priority are AWS - Storage. |
Not sure if Load Balancers and S3 Buckets really needed... instead EC2 Volumes... |
It seems that S3 are not necessary for WS 1.0. It could be the same for load balancers. Instead they need the EC-Volumes. |
@meshipeer According to @mihaitusa we should implement those functionalities using query API. |
@meshipeer It has began with CloudSlang/cs-actions#225 @Tirla-Alin should write down the .sl && test .sl files |
|
excellent work Mihai |
@chronical In cs-action are: DescribeAvailabilityZones, CreateSubnet, DeleteSubnet, ReleaseAddress, CreateLoadBalancer, DeleteLoadBalancer and Get Bucket (7) operations that don't have any .sl files associated. The content doesn't need it? |
they will be added when including the cs-actions. @alinaciobanca @tethryus @Madalin-HPE fyi. |
@chronical @alinaciobanca The Amazon integration is expanded enough? Worth keeping this US? |
@chronical Sad to see that are no updates in content related to the (10) missing ops.... |
@mihaitusa @angelhpe .. all in due time, we'll include this in the backlog @tethryus , can we generate the .sl-s using the tool? |
Amazon aws images #111
The text was updated successfully, but these errors were encountered: