Ocean bounty : AWS compute plugin for Brizo

[Anirudh2490]

EC2 Compute Plugin for Brizo

How can you help?

We want to implement the Computing EC2 plugin and write the test coverage cases for the same. Brizo is our technical component that interacts with external cloud infrastructure like AWS, Azure etc.

The reference to the AbstractPlugin module used in the Compute EC2 plugin can be seen here

Note - When we talk about Brizo here, we mean 3rd party developer app (in this case, Brizo).

Regarding this implementation, our assumptions about how user should be configuring AWS are (but feel free to point out our errors in this assumptions)

• Configure AWS Account to allow access to an external app (Brizo) using an AWS access and secret key pair.
• Configure your AWS Account to use ECS Fargate (create a cluster with VPC and subnets associated). To this point, please consider documenting or use some cloud management tool such as Terraform to provide a reproducible path.
• Create the needed IAM policy(ies) with the needed permissions (i.e.: creating a Fargate container, IAM create/pass role and manage policies...) and attach them to the Brizo’s user. Keep the policies permissions as restricted as possible.
• Also please consider to create IAM role and permissions to attach to the container run in Fargate. The container would need to be accessed in order to run the assets.
• You can create/modify the base image used to run the container. This base image would need to download and run a script located in S3, so the base entry point will need to access to a custom S3 location (in the same account), download and execute it.

Please refer to the required AWS SDK for this task. The version (boto3==1.8.7) is mentioned in the requirements as well.

Setup for the task

Before starting the task, you must do the following

• You will need to create an AWS user (with secret & access key) with a policy of minimal permissions. This would allow Brizo to run containers in the Fargate cluster.
• In order to do this, you will need to create your own AWS account. Everything that needs to be done in this task should be under the free tier.
• Creating users are documented in the AWS docs This task is ideally suited for devs that have some experience in AWS.

What needs to be done?

• EC2 Compute Plugin needs to have all the methods implemented in python.
• Unit tests for the same must also be written.

We are very happy when

• [ ] Our unit test coverage for EC2 Compute Plugin is >= 85%. We are using pytest framework for testing. We would require the new tests to be written using same setup.
• [ ] Pull request for this implementation should go in this repo - https://github.com/oceanprotocol/osmosis-aws-driver

Seen this problem before?

Any help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.

Questions & Reviews

Pull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)

Things to know

The bounty lifecycle process including payout will be managed using Gitcoin. We'll be responding to your questions here, but for discussion and clarification we recommend to join also our Gitter channel where our tech community is accessible. In order to see the PROCN balance in your wallet you'll need to reference the related token contract with address 0xf2aabdd898a0139195b2b5da7387d43a45ded254. If you use a Metamask plugin you'll find the the exact steps here.

Reward

Once the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (Ocean Token will be valued at at 0.22 EUR on network launch). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.

Lastly, even if it is a contest bounty, we will appropriately reward all valuable contributions. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! 😃

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 8000.0 PROCN attached to it as part of the Ocean Protocol Foundation fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  • Want to chip in? Add your own contribution here.
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  • $37,143.38 more funded OSS Work available on the Gitcoin Issue Explorer

[chalidbdb]

Welcome @cr2fx! Good to have you on bord. If you have any question or get stuck please post to our gitter channel: https://gitter.im/oceanprotocol/Lobby.

Please share here, how you are going to approach the work, what will be your steps and when you are planning to complete.

[Anirudh2490]

@cr2fx do let us know if you are able to progress. If any doubts, reach us on Gitter!

[cr2fx]

My debit card doesn't seem to get verified on AWS free tier :/ I've used it in past, so I do know how things work but I don't have an active account since I had switched to GCP recently.

[Anirudh2490]

@cr2fx I think if you've used a credit card in the past, it will not work beyond 12 months of free tier. Do you have another credit or debit card you can use?

[bobjiang]

@cr2fx Here is Bob Jiang from Gitcoin team, are you still working on this issue?

[Anirudh2490]

@neuroleptic unfortunately we will not be able to provide the free AWS tier. You should be able to set one up with a new email and card. Do let us know if you intend on pursuing this task as we are planning on resolving this internally if you are unable to do it.

[neuroleptic]

@Anirudh2490 I can still work on this. Is there a particular deadline when you would like it to be completed by?

[Anirudh2490]

@neuroleptic when do you think you can deliver it by?

[iamonuwa]

@Anirudh2490 I've applied to start work on this.

[iamonuwa]

@Anirudh2490 did you stop me from working?

[innopreneur]

@iamonuwa We are canceling this bounty because it seems specs are not upto date anymore and currently you might not get enough support from dev team as everyone is occupied with the upcoming network launch. We will reissue this bounty once we update the spec and assign you if you would still be hopefully interested in working on it. But, for now we don't want to see you or anyone else struggle with outdated docs. And hence we are cancelling this bounty.

[iamonuwa]

@iamonuwa We are canceling this bounty because it seems specs are not upto date anymore and currently you might not get enough support from dev team as everyone is occupied with the upcoming network launch. We will reissue this bounty once we update the spec and assign you if you would still be hopefully interested in working on it. But, for now we don't want to see you or anyone else struggle with outdated docs. And hence we are cancelling this bounty.

Hi @innoprenuer thank you for responding. Please reach out to me on gitcoin slack with @iamonuwa or on your gitter with same name anytime its up. Am very much available and eager to get this task done at anytime

[innopreneur]

@iamonuwa sure thing :+1:

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

The funding of 8000.0 PROCN attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $46,159.01 more funded OSS Work available on the Gitcoin Issue Explorer