
Create dashboard for managing cloud server
- or -
Post a project like this1796
$1.3k
- Posted:
- Proposals: 5
- Remote
- #3139968
- OPPORTUNITY
- Awarded
Description
Experience Level: Expert
Summary
I'm looking to partner with developer specialist to help achieve our goal of automating deployment, security, and management of thousands of cloud instances.
Providers
- CloudCone (https://api.cloudcone.com/) - RunCloud (https://runcloud.io/docs/api)
Scripting
We have a series of commands that need to be ran at the start up of each instance. Here is the link to the script file right now so you can see everything that we plan to execute.
**DISCLAIMER** There are a couple manual steps that we would love to automate and would need to get your advice on, otherwise that would be the commands that would need to be compiled into a batch file to run at the start up of every new cloud instance.
Process
Instance Creation
We would receive a POST request from the website to create an instance for a new customer. There would need to be a portal that keeps track of:
- Every instance that is online by the name assigned to it, a column with the IP address, and a column with the customer ID we receive from the site so we know who’s is what without disclosing personal information.
- Every hour the server is online from point of creation until the Instance Deletion request comes online.
- A text area that updates with the cumulative number of hours that all of the servers are online for. Example: If there are 100 servers and 50 of them have been online for 5 hours and 50 of them have been online for 10 hours, the number displayed would be 750.
- There are going to be thousands of these instances that we are going to be managing and
we get paid by the hour that these are online, so this is a CRITICAL piece that should
always be in operation.
- There will also be two different tiers of instances. So the cumulative number displayed
needs to correlate to which instance template. Example: Tier 1 - 10,421, Tier 2 - 3,513 - The portal would need login credentials for specific users to be able to access this
information.
Once that POST request is received, we would need the instance to run the batch file mentioned in Scripting above. After that has been successfully ran, we would then need to: - Add that instance to RunCloud,
- Update the Firewall settings to block port 80,
- Update the Firewall settings to block port 443, and
- Update the Firewall settings to allow port TCP 6080.
- As an additional measure, we would love to enable the option for Passwordless login for all
servers if that is possible within the API.
After the instance has been added to RunCloud successfully and the batch file has ran successfully, we would want to then send the server’s IP address, the Customer ID, and the password generated in the batch file for the VNC server so the site can notify the user their instance is ready for launch.
The website will display the IP address in a specific format and the password for users to log into the instance when they are logged in.
Instance Pausing
In case of a client’s billing were to pause, we need the ability to receive a command from the website to send a shut down command to the associated Customer ID’s instance.
For our billing purposes, for every 24 hours that an instance is paused we need to add an hour to the cumulative usage for all servers that is displayed.
If the Customer’s account is reactivated, then a command to turn the instance back on would need to be issued in order for that instance to turn on and be accessible once again.
Instance Deletion
In case of a client’s account being closed, we need to be able to receive a command from the website to delete an instance. Once that command is received, CloudCone needs to delete the correctly correlating instance to that Customer ID, update the hours total with how many hours that server was online.
In addition we need to remove that instance from RunCloud as well.
Additional Functionality
The total number of billing hours by tier that is calculated needs to be from 12:00a EST on the 1st of each month until 11:59p EST on the last day of each month.
Those hourly totals of all instances by tier needs to be able to be sent to our billing system to automatically update the invoice that is generated around 8a EST on the 1st. We bill by the hour, per tier. Those totals are CRITICAL for us to keep track of properly.
We use Zoho Books for our billing system.
An additional feature we need is the ability for a logged into user to the portal to upload a file that replaces an existing file on all of the instances. The file names won’t always match, but it’s always in the same location.
This should work with receiving requests from a system like WHMCS to create, pause, and delete the instances
The job needs to be completed in 15 days - After one week I need at least a draft version.
I'm looking to partner with developer specialist to help achieve our goal of automating deployment, security, and management of thousands of cloud instances.
Providers
- CloudCone (https://api.cloudcone.com/) - RunCloud (https://runcloud.io/docs/api)
Scripting
We have a series of commands that need to be ran at the start up of each instance. Here is the link to the script file right now so you can see everything that we plan to execute.
**DISCLAIMER** There are a couple manual steps that we would love to automate and would need to get your advice on, otherwise that would be the commands that would need to be compiled into a batch file to run at the start up of every new cloud instance.
Process
Instance Creation
We would receive a POST request from the website to create an instance for a new customer. There would need to be a portal that keeps track of:
- Every instance that is online by the name assigned to it, a column with the IP address, and a column with the customer ID we receive from the site so we know who’s is what without disclosing personal information.
- Every hour the server is online from point of creation until the Instance Deletion request comes online.
- A text area that updates with the cumulative number of hours that all of the servers are online for. Example: If there are 100 servers and 50 of them have been online for 5 hours and 50 of them have been online for 10 hours, the number displayed would be 750.
- There are going to be thousands of these instances that we are going to be managing and
we get paid by the hour that these are online, so this is a CRITICAL piece that should
always be in operation.
- There will also be two different tiers of instances. So the cumulative number displayed
needs to correlate to which instance template. Example: Tier 1 - 10,421, Tier 2 - 3,513 - The portal would need login credentials for specific users to be able to access this
information.
Once that POST request is received, we would need the instance to run the batch file mentioned in Scripting above. After that has been successfully ran, we would then need to: - Add that instance to RunCloud,
- Update the Firewall settings to block port 80,
- Update the Firewall settings to block port 443, and
- Update the Firewall settings to allow port TCP 6080.
- As an additional measure, we would love to enable the option for Passwordless login for all
servers if that is possible within the API.
After the instance has been added to RunCloud successfully and the batch file has ran successfully, we would want to then send the server’s IP address, the Customer ID, and the password generated in the batch file for the VNC server so the site can notify the user their instance is ready for launch.
The website will display the IP address in a specific format and the password for users to log into the instance when they are logged in.
Instance Pausing
In case of a client’s billing were to pause, we need the ability to receive a command from the website to send a shut down command to the associated Customer ID’s instance.
For our billing purposes, for every 24 hours that an instance is paused we need to add an hour to the cumulative usage for all servers that is displayed.
If the Customer’s account is reactivated, then a command to turn the instance back on would need to be issued in order for that instance to turn on and be accessible once again.
Instance Deletion
In case of a client’s account being closed, we need to be able to receive a command from the website to delete an instance. Once that command is received, CloudCone needs to delete the correctly correlating instance to that Customer ID, update the hours total with how many hours that server was online.
In addition we need to remove that instance from RunCloud as well.
Additional Functionality
The total number of billing hours by tier that is calculated needs to be from 12:00a EST on the 1st of each month until 11:59p EST on the last day of each month.
Those hourly totals of all instances by tier needs to be able to be sent to our billing system to automatically update the invoice that is generated around 8a EST on the 1st. We bill by the hour, per tier. Those totals are CRITICAL for us to keep track of properly.
We use Zoho Books for our billing system.
An additional feature we need is the ability for a logged into user to the portal to upload a file that replaces an existing file on all of the instances. The file names won’t always match, but it’s always in the same location.
This should work with receiving requests from a system like WHMCS to create, pause, and delete the instances
The job needs to be completed in 15 days - After one week I need at least a draft version.
Fabrizio R.
100% (3)Projects Completed
1
Freelancers worked with
1
Projects awarded
13%
Last project
16 Feb 2021
Italy
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies