Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
CloudPond
CloudPond
- Service Overview
- Getting Started
-
User Guide
- CloudPond Console Overview
- Edge Site
- Network Connectivity
- Cloud Resources
- Monitoring Data
- Enterprise Project Management
- Quota Adjustment
- Auditing
-
FAQs
- Popular Questions
- CloudPond Overview
- Security
- Billing
- Region and Edge site
-
Rack Installation
- How Do I Know Whether My On-premises Data Center Meets the CloudPond Location Requirements?
- Can I Install Third-Party Devices in the Racks?
- Who Will Install the Hardware and Software After the Racks Are Delivered to the Location?
- What Do I Need to Do Before, During, and After an Edge Site Is Deployed?
- Network Connectivity
- O&M
- Upgrade and Capacity Expansion
- Best Practices
- General Reference
On this page
Help Center/
CloudPond/
Best Practices/
CloudPond Best Practices of Edge-Cloud Networking/
Scenarios/
Local Deployment/
Deploying ERP Services on CloudPond
Copied.
Deploying ERP Services on CloudPond
Background
A customer uses CloudPond to avoid data security risks of their purchased SaaS ERP software. The service status is as follows:
- ERP is mainly used inside the company. So, it needs to be deployed locally for low latency.
- ERP needs to be used outside the company during business trips.
- ERP requires high reliability. It cannot be interrupted except during holidays for both internal and external use.
- The network and security system of the customer data center meets the ERP deployment requirements.
Networking Configuration
The recommended edge-cloud networking is shown in Figure 1.
Key Points
- The minimum bandwidth is provided for management plane and data plane networks because all services are deployed at the edge and the edge-cloud traffic is small.
- It is recommended that the public network of the data center is expanded for ERP use only because the network of the data center may be used by users outside the company.
- EIP billing by traffic is recommended for the default settings of edge-cloud communications because the cloud data plane does not need to communicate with the edge.
- It is recommended that load balancing is built for public network access, meeting the high reliability requirements of ERP services. The internal network of the data center does not need load balancing due to its maturity.
- The security system of the customer data center should cover ERP applications. If the security system cannot cover them, CloudPond can provide the security capabilities.
Parent topic: Local Deployment
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot