--- id: "en/deployment-service-flow" title: "Implementation process and initialization services" language: "en" description: "Pre-deployment preparation, implementation phase, initialization, training and data migration." canonical_url: "https://www.babel.cc/public/babelwiki/en/deployment-service-flow.html" markdown_url: "https://www.babel.cc/public/babelwiki/ai/en/deployment-service-flow.md" alternates: {"en": "https://www.babel.cc/public/babelwiki/ai/en/deployment-service-flow.md", "zh": "https://www.babel.cc/public/babelwiki/ai/zh/deployment-service-flow.md"} reading_note: "文档记录不等于当前部署能力;以实际版本、授权模块与配置为准。保留原文的可选、限制及待确认说明,勿补猜接口。 / Documentation is not a guarantee for every deployment. Preserve optional-module requirements, limitations and unresolved API contracts." --- # Implementation process and initialization service Privatization requirements and service procedures In order to ensure the experience and quality of using the BabelBird system, all privatized deployment work of BabelBird is deployed remotely or on-site and certificates are issued by the BabelBird team. Deployment by an agent team or self-deployment by customers is not currently supported. At the same time, the maintenance work of the system is also carried out by the Babel operation and maintenance team on a regular basis remotely. Customers only need to prepare the hardware and access resources as required, and leave the rest to the Babel team. Things that need to be prepared in the early stage of privatized deployment: Calculate the approximate number of users, concurrency, storage space and space growth rate and let the Babel account manager evaluate the required configuration. The customer evaluates the remaining resources (if any) of the existing server and selects a deployment method based on the actual situation. Babel issued a privatization deployment plan. Customers prepare corresponding servers and access resources according to the plan, allocate servers, and install operating systems. Provide deployment access through a customer-approved VPN, bastion host or on-site arrangement. Limit access duration, source addresses and ports to the implementation plan. For isolated networks, agree an offline delivery process; see the [POC guide](https://www.babel.cc/public/babelwiki/en/deployment-poc.html). Remote implementation does not require exposing SSH or remote desktop directly to the internet. It is best for the user to provide a domain name. If there is no domain name, a fixed IP address is required. The solution using IP address to access needs to ensure that the IP address will not change during use. If you need to access your email to retrieve your password or send a verification code to your mobile phone number, you need to prepare the corresponding email access or SMS gateway. | Number | Project | Requirements | Remarks | | --- | --- | --- | --- | | 1 | Domain name | An independent primary domain name or secondary domain name is required | A secondary domain name can be set based on the company's original domain name. Such as yun.company.com | | 2 | Email | An email address that can send notification emails is required | An email address that supports SMTP is sufficient ########## Email push related ########## MailUser=xxxx@mail.com MailPassword=password MailHost=Mail server address MailPort=Port number | | 3 | Implementation access | Customer-approved VPN, bastion host or on-site access | Time-limited and source-restricted; agree offline delivery for isolated networks | | 4 | SSl certificate | https needs to apply for an SSL certificate | Apply like a digital certificate authority CA. Recommended Application OV Wildcard | | 5 | SMS interface | If you need a mobile invitation, please register with your mobile phone. You need to activate the SMS interface service (optional) | Cloud service providers such as Alibaba Cloud and Tencent Cloud also provide SMS service interfaces, which can be activated by applying | implementation stage Notify us after the preparation work is completed, and we will give users a specific implementation time schedule. Keep the approved access path available during implementation; follow the agreed delivery process for offline or on-site work. Implementation generally takes 2-3 working days. On the first day, Babel is deployed and installed remotely, on the second day it is tested and accepted, and on the third day, problems encountered are corrected. Once the implementation is complete we will notify the user and then start the initialization phase Initialize service Babel provides initialization services to all private cloud customers, including: Maintenance personnel training (remote or on-site) Help users with data migration, user import, permission assignment, etc. (remotely or on-site) User training (remote or on-site)