CMDB Publishing platform: Go Release Management

This is a creation in Article, where the information may have evolved or changed.

The CMDB publishing platform is a release management platform for Ezbuy, which includes the release of Go, Windows Serices Publishing, IIS Publishing, Memcache management, SVN management, asset information management operations.

With the company's business development, the company go Service has more than 100 single instances, if the multi-machine deployment calculation, is multiplied by the number of growth, and the frequency of the daily update release, so if the person to publish, the following problems will occur:

1. Every time the developer update the service, we need to find the OPS staff to publish
2. Each release, no version information recorded, only the corresponding version number, that is, no historical data
3. Repetitive workloads, no technology, and easy to publish errors
4. No message notification
5. Developers are compiled on their own computers and then submitted to SVN (environment is not unified)

Go now release is automatically uploaded to svn after each Jenkis auto-compilation, avoid compiling the Mac OS version of Go upload to SVN, and then published via the CMDB platform, publishing involves manual and automatic release of two operations:

1. Manual: Developers manually publish via the CMDB platform
2. Automatic: After compiling, Jenkis directly calls the CMDB API to automatically publish to the online (continuous CD)

In summary, the CMDB developed the Go Release Management module, which includes the following features:

1. Deployment
2. Release
3. Update Go configuration file
4. Restart the Go service
5. Version rollback
6. Go Service Status
7. Go crontab release updates
8. Go Cron Job scheduled Task List

[Deploy]:

Online OPS personnel can deploy a new go service directly via the OPS platform

Go deployment

[Release]:

Developers have the right to directly publish the service to the online, without operator intervention, and each release to fill in the corresponding tower publishing URL, or not to give the release

Go release

Regardless of the success of the service, the CMDB invokes the Spike API to send the results to the Spike message group, and the CMDB saves a log to the database.

Go post message

[Update go profile]:

Go configuration file We will separate all the go instance configuration files in an SVN repository, the advantage is that there is version control, to avoid the developer of human changes, and sensitive information only the corresponding permissions of the people to view, so every time the configuration file change table, directly corresponding to the right to submit to SVN, By updating all hosts issued by the Go configuration file:

Go Distribution configuration file

[Version rollback]:

On-line OPS students can roll back to the appropriate version via the CMDB platform

[Service status]:

Developers can see the status of the Go service running in real time

[Go crontab UPDATE]:

Developers can publish the Go service directly

[Cron Job list]:

You can view all cron jobs and cron job last execution time on the CMDB platform

Finally, we will be the same as the Go profile online and offline environment, and do not expose sensitive information, please pay attention to the next article "How to use Consul-template to keep online and offline configuration file consistent"