Server Provisioning - deployERP - Odoo Server Management

Overview

Server provisioning in deployERP is a streamlined process that creates optimized infrastructure for your Odoo deployments. This guide covers everything from initial setup to advanced provisioning options.

Prerequisites

Before provisioning a server, ensure you have:

Cloud Provider Connected

At least one cloud provider configured in your account

Sufficient Permissions

Appropriate permissions in your cloud provider account

Provisioning Process

Select Provider

Choose from your connected cloud providers

Configure Server

Set location, size, and specifications

Review Settings

Confirm configuration and costs

Deploy

Initiate automated provisioning

Monitor Progress

Track provisioning status in real-time

Server Configuration Options

Basic Settings

string

required

Unique server identifier (e.g., “production-eu-1”)

Must be lowercase
Can contain hyphens
3-50 characters

string

required

Cloud provider selection:

aws - Amazon Web Services
digitalocean - DigitalOcean
azure - Microsoft Azure
vultr - Vultr
hetzner - Hetzner Cloud
gcp - Google Cloud Platform

string

required

Deployment region based on provider:AWS Regions:

us-east-1 - US East (N. Virginia)
eu-west-1 - EU (Ireland)
ap-southeast-1 - Asia Pacific (Singapore)

DigitalOcean Regions:

nyc3 - New York
lon1 - London
sgp1 - Singapore

Server Specifications

string

required

Server size configuration:

Size	vCPU	RAM	Storage	Monthly Cost*
`small`	2	4GB	80GB	~$40
`medium`	4	8GB	160GB	~$80
`large`	8	16GB	320GB	~$160
`xlarge`	16	32GB	640GB	~$320
`custom`	Variable	Variable	Variable	Variable

*Costs vary by provider and region

Advanced Options

string

default:"3.10"

Python version for Odoo compatibility:

3.8 - For Odoo 14 and older
3.9 - For Odoo 15
3.10 - For Odoo 16-17 (recommended)
3.11 - Latest version

string

default:"14"

PostgreSQL database version:

12 - Legacy support
13 - Stable
14 - Recommended
15 - Latest features

string

default:"ssd"

Storage configuration:

ssd - Standard SSD (recommended)
nvme - High-performance NVMe
hdd - Cost-effective HDD

Provisioning via Dashboard

Step 1: Navigate to Servers

From your deployERP dashboard:

Click Servers in the navigation
Click New Server button

Step 2: Provider Selection

Existing Provider
New Provider

Select from your connected providers:

Choose provider from dropdown
Verify available regions
Check resource quotas

Step 3: Server Configuration

Configure your server specifications:

# Example configuration
name: production-server
provider: digitalocean
region: nyc3
size: large
python_version: "3.10"
postgresql_version: "14"
storage_type: ssd

Step 4: Review and Deploy

Review configuration summary
Verify estimated costs
Check provider quotas
Click Deploy Server

Provisioning via API

curl -X POST https://api.deployerp.com/v1/servers \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production-server",
    "provider": "digitalocean",
    "region": "nyc3",
    "size": "large",
    "python_version": "3.10",
    "postgresql_version": "14"
  }'

import deployerp

client = deployerp.Client(api_key="YOUR_API_KEY")

server = client.servers.create(
    name="production-server",
    provider="digitalocean",
    region="nyc3",
    size="large",
    python_version="3.10",
    postgresql_version="14"
)

print(f"Server ID: {server.id}")
print(f"Status: {server.status}")

const deployerp = require('@deployerp/sdk');

const client = new deployerp.Client({ apiKey: 'YOUR_API_KEY' });

const server = await client.servers.create({
  name: 'production-server',
  provider: 'digitalocean',
  region: 'nyc3',
  size: 'large',
  pythonVersion: '3.10',
  postgresqlVersion: '14'
});

console.log(`Server ID: ${server.id}`);
console.log(`Status: ${server.status}`);

Provisioning Timeline

Typical provisioning times by provider:

Provider	Small	Medium	Large	XLarge
DigitalOcean	2-3 min	3-4 min	4-5 min	5-7 min
AWS	3-5 min	4-6 min	5-7 min	7-10 min
Azure	5-7 min	6-8 min	8-10 min	10-15 min
Vultr	2-3 min	3-4 min	4-5 min	5-7 min

Provisioning Progress

Track provisioning status in real-time:

Status Indicators

Status	Description	Progress
`provisioning`	Server being created	0-30%
`configuring`	Installing software	30-60%
`optimizing`	Performance tuning	60-80%
`finalizing`	Security setup	80-95%
`running`	Ready for use	100%

Progress Monitoring

{
  "status": "configuring",
  "progress": 45,
  "current_step": "Installing PostgreSQL",
  "steps_completed": [
    "Server created",
    "Network configured",
    "OS installed"
  ],
  "estimated_time_remaining": "3 minutes"
}

Post-Provisioning Setup

Once provisioning completes:

Verify Server Status

Confirm server shows as “running”

Check Resources

Review CPU, RAM, and storage allocation

Configure SSH Keys

Add SSH keys for direct access

Set Up Monitoring

Enable alerts and notifications

Deploy First Instance

Create your first Odoo instance

Custom Server Provisioning

For specific requirements:

Bring Your Own Server

Connect existing servers:

Install deployERP agent
Register with platform
Configure management
Enable monitoring

# Install agent on existing server
curl -sSL https://get.deployerp.com | bash
deployerp-agent register --token=YOUR_TOKEN

Custom Specifications

Request custom configurations:

High memory instances (up to 512GB)
GPU-enabled servers
Dedicated hosts
Custom networking

Contact support for custom server configurations not available in standard options.

Multi-Region Deployment

Deploy servers across regions:

Benefits

Reduced latency
Data sovereignty
Disaster recovery
Load distribution

Configuration

regions:
  - name: production-us
    provider: aws
    region: us-east-1
    size: large
  - name: production-eu
    provider: aws
    region: eu-west-1
    size: large
  - name: production-asia
    provider: aws
    region: ap-southeast-1
    size: medium

Cost Optimization

Right-Sizing

Choose appropriate server sizes:

Monitor actual usage
Scale based on metrics
Use development servers for testing
Consider time-based scaling

Reserved Instances

Save on long-term deployments:

AWS Reserved Instances
Azure Reserved VMs
Committed use discounts

Spot Instances

For non-critical workloads:

Up to 90% cost savings
Suitable for development
Batch processing
Testing environments

Troubleshooting

Common Issues

Issue	Cause	Solution
Provisioning fails	Quota exceeded	Increase provider limits
Slow provisioning	Region congestion	Try different region
Connection timeout	Network issues	Check firewall rules
Invalid configuration	Unsupported options	Verify compatibility

Error Handling

{
  "error": {
    "code": "quota_exceeded",
    "message": "vCPU quota exceeded in region us-east-1",
    "details": {
      "current_usage": 95,
      "quota": 100,
      "requested": 8
    },
    "suggested_action": "Request quota increase or use different region"
  }
}

Best Practices

Plan Capacity

Estimate resource needs before provisioning

Use Naming Conventions

Consistent naming for easy management

Document Configuration

Keep records of server specifications

Test First

Provision test servers before production

Next Steps

After provisioning your server:

​Overview

​Prerequisites

Cloud Provider Connected

Sufficient Permissions

​Provisioning Process

​Server Configuration Options

​Basic Settings

​Server Specifications

​Advanced Options

​Provisioning via Dashboard

​Step 1: Navigate to Servers

​Step 2: Provider Selection

​Step 3: Server Configuration

​Step 4: Review and Deploy

​Provisioning via API

​Provisioning Timeline

​Provisioning Progress

​Status Indicators

​Progress Monitoring

​Post-Provisioning Setup

​Custom Server Provisioning

​Bring Your Own Server

​Custom Specifications

​Multi-Region Deployment

​Benefits

​Configuration

​Cost Optimization

​Right-Sizing

​Reserved Instances

​Spot Instances

​Troubleshooting

​Common Issues

​Error Handling

​Best Practices

Plan Capacity

Use Naming Conventions

Document Configuration

Test First

​Next Steps

Overview

Prerequisites

Provisioning Process

Server Configuration Options

Basic Settings

Server Specifications

Advanced Options

Provisioning via Dashboard

Step 1: Navigate to Servers

Step 2: Provider Selection

Step 3: Server Configuration

Step 4: Review and Deploy

Provisioning via API

Provisioning Timeline

Provisioning Progress

Status Indicators

Progress Monitoring

Post-Provisioning Setup

Custom Server Provisioning

Bring Your Own Server

Custom Specifications

Multi-Region Deployment

Benefits

Configuration

Cost Optimization

Right-Sizing

Reserved Instances

Spot Instances

Troubleshooting

Common Issues

Error Handling

Best Practices

Next Steps