Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Right now I am using the Auto Scaling Command Line Tool to launch a new EC2 instance once per day and run a script that terminates itself upon completion. Now I need to do the same thing with a different script, but this one requires several Python modules to be installed. Therefore, I would like to schedule the start/stop of a single, existing instance rather than the launch/termination of a brand new instance. I've scoured Amazon's documentation/blogs but I can't determine if this functionality is supported with Autoscaling. How could this be accomplished?
Its not supported with autoscaling. If you want to keep doing what you are currently doing. You could install the python modules with a cloud init script.
You can also start/stop an existing instance with the command line tools, just not the autoscaling ones.
My eventual solution was to set up an instance the way I wanted and then create an AMI from it. My autoscaling setup then starts/stops an instance of that AMI.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
Hi I am fairly new to the Ansible and Terraform world. We need to install Ansible from Terraform script. I have the script to install Ansible but want to know what is the best way to call that script from Terraform to make sure the script is called after the Virtual Machine is created. I have been reading about local-exec and remote-exec methods but they are not recommended by TF. Any help on the topic would be appreciated!
From terraform yeah, you don't have much of a choice really.
The only way to do it is to use remote-exec provisioners as you said.
They are not recommended because terraform can't guarantee that they'll succeed. What I mean by this is, if the commands you give to provisioner fail, terraform will move on because it can't know the exit status of provisioners and commands you gave them.
What I would recommend you if you are able to and if that matches your use case is to use packer.
Packer is used for making images which later you use as a template for your instances. You configure your image by passing commands and/or scripts to the packer. That way you can run sudo apt install ansible or whatever the command is once in packer and from that point use that image wherever you need.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I have a droplet on Digital Ocean and it becomes really slow some times when I have 30-40+ users at the same time. I don't know if its the droplets capacity or my code I didn't optimise well, but it's starting to become annoying. Are there any tips to inscrease the speed of my droplet?
Here's my droplet configs:
What can I do? Should I transfer on another hosting service? Is there any configs or options I can edit or add to my droplet to increase my server's speed?
EDIT:
Sorry, I should've specified what is it my droplet is running!
I'm actually running a Laravel 5.8 app with a MySQL database. I did my own multi-tenants system so people can have their own version of my app (ex.: People can create leagues that will create a database for each league, and every leagues are independant).
I'm not familiar with all of that, but when I do the htop command on my server I get this, I believe there is one mysqld process for each league (database) on my web app.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 days ago.
Improve this question
I have a Ruby code that I would like to run on AWS. Is is possible to run Ruby code on AWS?
You can run Ruby scripts on anything that has Ruby installed.
AWS (Amazon Web Services) provides you with a suite of tools to host servers (among other things). So your question "is it possible to run a simple ruby code on amazon AWS?" makes almost no sense at all. However, if you host an AWS server with some operating system, such as Ubuntu, then all you need to do is install Ruby, but it typically comes pre-installed on Linux.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am planning to deploy my developments from one instance to another, how should i proceed, what is the best practice about this process, I want to deploy DB objects(Tables, packages, views etc.) and application objects (Concurrent programs, messages, lookups etc.), Thanks for help.
The best practice to deploy database objects is
Have creation/modification script text files stored in a version control system.
Run the scripts from version control with sqlplus.
Note that you don't create/modify database objects in database with a GUI-tool but write the SQL in text files with a text editor.
The best practice to deploy eBS objects is
Save the objects from an eBS instance to text files with Generic Loader fndload.
Save the text files into a version control system.
Load the text files to another eBS instance(s) with fndload.
Here the objects are created in one eBS instance and then saved in to version control system and copied to other instances.
fndload example for concurrent programs:
ebs-1$ FNDLOAD apps/<PASSWD> O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct <CONCURRENT_NAME>_program.ldt PROGRAM APPLICATION_SHORT_NAME=<APP_NAME> CONCURRENT_PROGRAM_NAME=<CONCURRENT_NAME>
ebs-2$ FNDLOAD apps/<PASSWD> O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct <CONCURRENT_NAME>_program.ldt -
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
The Linux server I'm deploying a web application to has a rather outdated version of Ruby (1.8.7) in their repositories, and it doesn't look like that's going to change any time soon.
What are my options in terms of using other ruby versions than the distro sanctioned package in a production environment?
If I was to use something like rvm, how would that affect my deployment process, server management, and stability?
rvm or rbenv are your best bets for managing multiple ruby versions.
As long as you setup RVM/rbenv for the user you're going to be deploying to, this will work fine. In fact, I've done this myself on AWS with Capistrano.