Skip to main content

How to select cloud provider.



So we choose the cloud provider for the project. What I would
recommend and for whom:

1. For a project that starts from scratch with a single server. Where
the project will be some time in development, and the load will
increase gradually. I recommend Digital Ocean. 30 GB SSD drive and 1GB
RAM is cheap, fast and enough to deploy the project. Very simple and
intuitive interface make it easy to go to the schema with an service
per instance when load increases. Simple clone the original droplet
and leave just one or part service on new droplet. The main advantages
in this case lowest price and easy of deployment.

2. If you plan to transfer to the cloud the complex, high loaded
project from multiple servers, you should pay attention to Amazon.
Greater flexibility, a large selection of OS images. Allow easier and
faster to transfer existing services. A wide range of additional
services to reduce the cost and simplify the operation of the project
as compared to the "bare metal" solution. Among the many services
Amazon you will find easy replacement of each of the components of
your project.

3. If you start from scratch to develop highly loaded
service(application). If you need a flexible multi-functional
environment. With the ability to deploy services in one click. You can
pay attention to the GCE. In this case, the ability to deploy virtual
machines rather secondary. Compared with possibility for developers
and resources provided by Google App Engine. It is extremely
inexpensive to operate a solution "application as service". The
project can be built in such a way that each user will pay for itself
the resources used.

Please note it's my own (DevOps) view of question. Each case requires
a individual approach. If you have any questions you can connect to our team of cloud experts. We provide:
  • Cloud Consulting
  • DevOps services
  • Fully Managed Infrastructure
  • Cloud inventorying
  • Monitoring & Crash Prevention
Author: Ilya Shevyrev
Provided by:Forthscale systems, cloud experts

Comments

Popular posts from this blog

How to set or disable auto-logout on bash shell

Following information is intended for bash shell only.
The system variable TMOUT can be set to specify the amount of time the user is inactive before the user is automatically logged out.
Set the following listed below in the /root/.bashrc file: TMOUT=XXX #
The system will logout the root account after one hour of inactivity. The value entered for the TMOUT= variable is in seconds. To represent 1 hour, we have to multiply as follows: 1 hour is 60 minutes. 60 minutes * 60 seconds = 3600 seconds.
After setting the parameter, the intended user will need to log out and then log in for the changes to take effect. To make modifications apply to all users on the system, specify the TMOUT variable in /etc/ profile.
To disable auto-logout simply comment out or delete the line with TMOUT value

Provided by:Forthscale systems, cloud experts

How to install PGPool II on PostgreSQL Servers in master-slave architecture + PGPoolAdmin web managment

General InformationPGPool can run on same server along with PostgreSQL DB or on stand alone server(recommended). In this article we will install PGPool on stand alone server, but the only difference is connection ports on PGPool and PostgreSQL. We will install PGPool II 3.1 on PostgreSQL 9.1.


Basic architecture: ┏───────────────┓ │                │ │    pgpool-1    │ │  pgpool server │ │                │ ┗───────────────┛ //             \\ //               \\ //                 \\ \\//                \\// \/                  \/ ┏───────────────┓           ┏───────────────┓ │                │           │                │ │    pgsql-1     │ streaming │     pgsql-2    │ │  pgsql master  │══════════>│  pgsql slave   │ │     server     │replication│     server     │ │                │           │                │ ┗───────────────┛           ┗───────────────┛


Fail cases:Slave failsIn case slave server will fail PGPool will start failover.sh script and will mark server as Down (state 3). I…

Setting Filezilla Server on Amazon EC2 instance with passive ftp

If you want to set Filezilla  ftp server to handle passive connections on your AWS EC2 instances, you should do the following.

Select non used TCP ports, for example 9024-9048 range

Configure firewalls:

In your AWS EC2 security group, allow the incoming connections on chosen ports:

tcp port 20
tcp port 21
tcp port 9024-9048

If using Windows firewall  on you instance, allow connections on same ports.

Now configure Filezilla to use specific port range on Passive connections:

Open Filezilla management console.

Got to: Edit > Settings > Passive Mode Settings

'External Server IP Address for passive mode transfers'

If you use AWS Elastic IP, enter it in "Use the following IP",
if not - use Filezilla provided web service with "Retrieve external IP address from" option.

Check 'Don't use external IP for local connections'

Check 'Use custom port range'

Enter chosen values (in our example) 9024 - 9048 for custom port range.

Powered by 123Con…