Since the SREWorks v1.0 version was open sourced in March, the team has received various feedbacks through channels such as DingTalk, WeChat, and GitHub. Immediately, the team started the function optimization iteration of the v1.1 version, giving priority to solving the TOP3 problems reported by users:Storage plug-in, minimal resource deployment, storage class usageAt the same time, it has also made corresponding optimizations for the small problems exposed by users during the use process.

Subsequent products will continue to maintain a relatively fast release frequency, quickly solve the pain points reported by users in various channels, and help users use SREWorks to better build a cloud-native digital intelligence operation and maintenance platform.

The following is an introduction to the new features in this v1.1 release:

1. Basic Edition/Digital Edition

The resource consumption of the k8s cluster discourages many early adopters. Therefore, the v1.1 version separates the deployment of basic applications and digital applications, allowing users to experience only the base platform of SREWorks without opening the more resource-intensive digital applications.

The basic version of SREWorks isSingle 4-core 16GThe machine can start normally.

The basic application contains 8 applications:

• Operation and maintenance center

• Application management

• team management

• Cluster management

• Template Center

• Help Center

• file management

• system settings

The digital intelligence application includes 7 applications:

• Data operation and maintenance platform

• Intelligent operation and maintenance platform

• self-healing

• health management

• Operations Center

• Job scheduling platform

• Operation and maintenance search

When deploying helm, pass in the following parameters to use the basic version (the default is the digital version):

--set saas.onlyBase=true

2. Component plugging and unplugging: ElasticSearch/MySQL/MinIO

At present, the production environments of many companies include reliable storage modules, such as ES/MySQL/MinIO, etc., so some users do not want to use the storage modules that come with SREWorks v1.0 when deploying applications, but want to use those storage modules The endpoint of the middleware is injected directly.

After sorting and optimization, the team extracted variables from various storage modules used in SREWorks to support users’ modification during deployment.

When deploying helm, you can pass in the following parameters as required:

# 替换基础应用的主MySQL数据库
# MySQL这块需要注意，通常将主MySQL数据库和数智化MySQL数据库(吞吐较大)分成两个

--set appmanager.server.database.host="*.mysql.rds.aliyuncs.com" 
--set appmanager.server.database.password="****"
--set appmanager.server.database.user="root"
--set appmanager.server.database.port=3306
--set appmanagerbase.mysql.enabled=false

# 替换数智化应用的MySQL数据库
--set saas.dataops.dbHost="*.mysql.rds.aliyuncs.com"
--set saas.dataops.dbUser=root
--set saas.dataops.dbPassword="*****"
--set saas.dataops.dbPort=3306

# 替换数智化应用的ElasticSearch
--set saas.dataops.esHost="*.public.elasticsearch.aliyuncs.com"
--set saas.dataops.esPort="9200"
--set saas.dataops.esUser="elastic"
--set saas.dataops.esPassword="*******"

# 替换基础应用的MinIO存储
--set global.minio.accessKey="*******"
--set global.minio.secretKey="*******"
--set appmanager.server.package.endpoint="minio.*.com:9000"
--set appmanagerbase.minio.enabled=false

3. Page Template Center

The low-code front-end development model still has a certain threshold for users who have not been exposed to related applications before, so the team borrowed the concept of document templates and arranged front-end components into templates according to common scene categories, allowing users to quickly import A ready-made template page to continue front-end development on top of the template.

At the same time, the v1.1 version also supports users to save their commonly used pages as templates to improve the efficiency of daily page development.

4. Default storage class support

Many users who use k8s do not know the logic of using StorageClass, and often spend a lot of time on troubleshooting this problem.

After a comprehensive analysis and comparison of various community storage solutions, the v1.1 version uses the OpenEBS-based solution, providing users with a default LocalPV solution to reduce your usage costs.

Users must pay attention when using, if you use your own storage set or the k8s cluster already has a storage class, be sure to set this defaultstoragekindThe corresponding storage supply openebs is closed, otherwise the problem of storage directory contention is likely to occur.

The helm parameters for turning off the default storage class scheme of SREWorks are as follows. Take the storage class alicloud-disk-available of Alibaba Cloud ACK cluster as an example:

--set appmanagerbase.openebs.enabled=false
--set global.storageClass="alicloud-disk-available"

5. Other optimizations

• Solve the error of the edit page of the back-end microservice

• Added default authentication switch for backend microservices

• Solve the operation and maintenance application deletion error

• Solve the idempotent exception of appmanager multiple initialization

• Solve the error when importing productopsv2 in the slow database scenario (also valid for the NFS slow database scenario)

• Data source password box takes password input

6. How to upgrade from current version to v1.1

• The upgrade includes the base, so the page may be inaccessible for 5-10 minutes, please pay attention.

• Cloud native applications developed by users will not be affected (no restart), and the traffic from the SREWorks gateway to the application will be interrupted.

git clone http://github.com/alibaba/sreworks.git -b v1.1 sreworks
cd sreworks./sbin/upgrade-cluster.sh --kubeconfig="****"

If you encounter problems during use, you are welcome to submit Issues or Pull requests in GitHub.

SREWorks open source address:

https://github.com/alibaba/sreworks

More open source project collections:

https://www.aliyun.com/activity/bigdata/opensource_bigdata__ai