备案控制台
探索云世界
开发者社区 开发与运维 文章 正文

运维调试记录：Ubuntu14.04下部署Opendaylight Nitrogen集群

2018-03-21 1548
版权
版权声明：
本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《 阿里云开发者社区用户服务协议》和 《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写 侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
简介： 版权声明：本文为博主原创文章，未经博主允许不得转载。 https://blog.csdn.net/zhaobryant/article/details/79638755 建议参考...
版权声明：本文为博主原创文章，未经博主允许不得转载。 https://blog.csdn.net/zhaobryant/article/details/79638755

建议参考官网教程：Setting Up Clustering

一、实验环境

  • 主机节点系统版本： Ubuntu 14.04 (64bit)
odl@mpodl:~$ uname -a
Linux mpodl 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  • 主机节点硬件配置：单核CPU+4GB内存+50GB硬盘
odl@mpodl:~$ sudo lshw        
    description: Computer
    product: Standard PC (i440FX + PIIX, 1996) ()
    vendor: QEMU
    version: pc-i440fx-trusty
    width: 64 bits
    capabilities: smbios-2.4 dmi-2.4 vsyscall32
    configuration: boot=normal uuid=053D43B6-2E3C-CEA4-4C52-833DDD1749BE
  *-core
       description: Motherboard
       physical id: 0
     # CPU信息 
     *-cpu
          description: CPU
          product: QEMU Virtual CPU version 2.0.0
          vendor: Intel Corp.
          physical id: 401
          bus info: cpu@0
          slot: CPU 1
          size: 2GHz
          capacity: 2GHz
          width: 64 bits
     # 内存信息
     *-memory
          description: System Memory
          physical id: 1000
          size: 4GiB
     # 硬盘信息
     *-disk
           description: ATA Disk
           product: QEMU HARDDISK
           physical id: 0.0.0
           bus info: scsi@0:0.0.0
           logical name: /dev/sda
           version: 0
           serial: QM00001
           size: 50GiB (53GB)
           *-volume:0
                description: EXT4 volume
                vendor: Linux
                physical id: 1
                bus info: scsi@0:0.0.0,1
                logical name: /dev/sda1
                logical name: /
                version: 1.0
                serial: 65d80188-ddfb-4f08-8018-a0c2e1da8af3
                size: 46GiB
                capacity: 46GiB
           *-volume:1
                description: Extended partition
                physical id: 2
                bus info: scsi@0:0.0.0,2
                logical name: /dev/sda2
                size: 4093MiB
                capacity: 4093MiB
  • 集群环境：3台主机节点
Cluster_Node1: Ubuntu 14.04 -- [IP_Addr]=192.168.1.124
Cluster_Node2: Ubuntu 14.04 -- [IP_Addr]=192.168.1.125
Cluster_Node3: Ubuntu 14.04 -- [IP_Addr]=192.168.1.104

二、部署方法

1. 下载Opendaylight Nitrogen

在每台主机节点上执行如下命令，下载tar.gz格式的压缩包到用户目录下的ODL_N子目录：

odl@mpodl:~/ODL_N$ wget -P . https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/integration/karaf/0.7.2/karaf-0.7.2.tar.gz

或在官网下载，然后通过xftp软件从本地上传到服务器的Opendaylight运行环境中。

官网地址：https://www.opendaylight.org/technical-community/getting-started-for-developers/downloads-and-documentation

2. 安装Opendaylight Nitrogen

在每台主机节点上执行如下命令，解压压缩包到ODL_N子目录：

odl@mpodl:~/ODL_N$ tar -zxvf karaf-0.7.2.tar.gz

解压完成，即认为Opendaylight Nitrogen安装成功。

3. 配置Opendaylight Nitrogen集群

在每台主机节点下执行如下命令，完成集群脚本配置工作：

命令格式：sudo bash ./karaf-0.7.2/bin/configure_cluster.sh [index] [seed_node_list]

其中，[index]为正整数，表示在[seed_node_list]中对应哪个主机节点上配置集群脚本。另外，[seed_node_list]是组成集群的各个主机节点对应的IP地址列表，以空格或逗号隔开。

因此，具体执行命令如下：

# Cluster_Node1: IP=192.168.1.124
odl@mpodl:~/ODL_N$ sudo bash ./karaf-0.7.2/bin/configure_cluster.sh 1 192.168.1.124 192.168.1.125 192.168.1.104

# Cluster_Node2: IP=192.168.1.125
odl@mpodl:~/ODL_N$ sudo bash ./karaf-0.7.2/bin/configure_cluster.sh 2 192.168.1.124 192.168.1.125 192.168.1.104

# Cluster_Node3: IP=192.168.1.104
odl@mpodl:~/ODL_N$ sudo bash ./karaf-0.7.2/bin/configure_cluster.sh 3 192.168.1.124 192.168.1.125 192.168.1.104

当执行完之后，结果如下所示：

# Cluster_Node1: IP=192.168.1.124
odl@mpodl:~/ODL_N$ sudo bash ./karaf-0.7.2/bin/configure_cluster.sh 1 192.168.1.124 192.168.1.125 192.168.1.104
################################################
##             Configure Cluster              ##
################################################
Configuring unique name in akka.conf
Configuring hostname in akka.conf
Configuring data and rpc seed nodes in akka.conf
modules = [

    {
        name = "inventory"
        namespace = "urn:opendaylight:inventory"
        shard-strategy = "module"
    },
    {
        name = "topology"
        namespace = "urn:TBD:params:xml:ns:yang:network-topology"
        shard-strategy = "module"
    },
    {
        name = "toaster"
        namespace = "http://netconfcentral.org/ns/toaster"
        shard-strategy = "module"
    }
]
Configuring replication type in module-shards.conf
################################################
##   NOTE: Manually restart controller to     ##
##         apply configuration.               ##
################################################

备注：

（1）执行如上命令后，会在karaf-0.7.2/configuration目录下生成initial子目录，结果如下所示：

odl@mpodl:~/ODL_N$ ls ./karaf-0.7.2/configuration/
context.xml  factory  initial  logback.xml  tomcat-logging.properties  tomcat-server.xml

odl@mpodl:~/ODL_N$ ls ./karaf-0.7.2/configuration/initial/
akka.conf  modules.conf  module-shards.conf

可见，集群配置脚本在initial子目录下生成了akka.conf、modules.conf和module-shards.conf三个配置文件。

（2）查看第一台Ubuntu主机节点的akka.conf文件内容，具体如下所示：

odl@mpodl:~/ODL_N$ cat ./karaf-0.7.2/configuration/initial/akka.conf 

odl-cluster-data {
  akka {
    remote {
      artery {
        enabled = off
        canonical.hostname = "192.168.1.124"   # 本机IP地址
        canonical.port = 2550
      }
      netty.tcp {
        hostname = "192.168.1.124"             # 本机IP地址
        port = 2550
      }
      # when under load we might trip a false positive on the failure detector
      # transport-failure-detector {
        # heartbeat-interval = 4 s
        # acceptable-heartbeat-pause = 16s
      # }
    }

    cluster {
      # Remove ".tcp" when using artery.
      # 集群节点列表
      seed-nodes = ["akka.tcp://opendaylight-cluster-data@192.168.1.124:2550",
                "akka.tcp://opendaylight-cluster-data@192.168.1.125:2550",
                "akka.tcp://opendaylight-cluster-data@192.168.1.104:2550"]

      roles = ["member-1"]

    }

    persistence {
      # By default the snapshots/journal directories live in KARAF_HOME. You can choose to put it somewhere else by
      # modifying the following two properties. The directory location specified may be a relative or absolute path. 
      # The relative path is always relative to KARAF_HOME.

      # snapshot-store.local.dir = "target/snapshots"
      # journal.leveldb.dir = "target/journal"

      journal {
        leveldb {
          # Set native = off to use a Java-only implementation of leveldb.
          # Note that the Java-only version is not currently considered by Akka to be production quality.

          # native = off
        }
      }
    }
  }
}

同样地，第二台和第三台Ubuntu主机节点的akka.conf文件内容相似，只是对应的IP地址不同。

（3）查看第一台Ubuntu主机节点的module-shards.conf文件内容，具体如下所示：

odl@mpodl:~/ODL_N$ cat ./karaf-0.7.2/configuration/initial/module-shards.conf 
module-shards = [
    {
        name = "default"
        shards = [
            {
                name = "default"
                replicas = ["member-1",
                "member-2",
                "member-3"]
            }
        ]
    },
    {
        name = "inventory"
        shards = [
            {
                name="inventory"
                replicas = ["member-1",
                "member-2",
                "member-3"]
            }
        ]
    },
    {
        name = "topology"
        shards = [
            {
                name="topology"
                replicas = ["member-1",
                "member-2",
                "member-3"]
            }
        ]
    },
    {
        name = "toaster"
        shards = [
            {
                name="toaster"
                replicas = ["member-1",
                "member-2",
                "member-3"]
            }
        ]
    }
]

同样地，第二台和第三台Ubuntu主机节点的module-shards.conf文件内容完全相同。

4. 启动Opendaylight Nitrogen集群

在每台主机节点下执行如下命令，完成Opendaylight节点启动工作：

odl@mpodl:~/ODL_N$ ./karaf-0.7.2/bin/karaf 
karaf: JAVA_HOME not set; results may vary
Apache Karaf starting up. Press Enter to open the shell now...
100% [========================================================================]
Karaf started in 8s. Bundle stats: 208 active, 209 total

    ________                       ________                .__  .__       .__     __       
    \_____  \ ______   ____   ____ \______ \ _____  ___.__.|  | |__| ____ |  |___/  |_     
     /   |   \\____ \_/ __ \ /    \ |    |  \\__  \<   |  ||  | |  |/ ___\|  |  \   __\    
    /    |    \  |_> >  ___/|   |  \|    `   \/ __ \\___  ||  |_|  / /_/  >   Y  \  |      
    \_______  /   __/ \___  >___|  /_______  (____  / ____||____/__\___  /|___|  /__|      
            \/|__|        \/     \/        \/     \/\/            /_____/      \/          


Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight.

opendaylight-user@root>

然后，执行命令feature:list -i检查odl-mdsal-clustering是否处于已安装状态。如果没有安装，则执行命令feature:install odl-mdsal-clustering完成对应Feature的安装。

opendaylight-user@root>feature:list -i
Name                            | Version | Required | State   | Repository                      | Description
----------------------------------------------------------------------------------------------------------------------------------------------------
odl-mdsal-broker                | 1.6.2   |          | Started | odl-mdsal-1.6.2                 | odl-mdsal-broker
odl-mdsal-clustering            | 1.6.2   | x        | Started | odl-mdsal-clustering            | odl-mdsal-clustering

5. 检查Opendaylight Nitrogen集群是否建立

在每台主机节点下执行如下命令，获取主机节点的角色信息（Leader/Follower）：

opendaylight-user@root> ld | grep clustering

于是，在主机节点一，输出如下：

2018-03-21 13:22:45,688 | INFO  | d-dispatcher-125 | Shard                            | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-prefix-configuration-shard-config (Candidate): Starting new election term 21
2018-03-21 13:22:45,741 | INFO  | d-dispatcher-125 | Shard                            | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-prefix-configuration-shard-config (Candidate) :- Switching from behavior Candidate to Leader, election term: 21
2018-03-21 13:22:45,742 | INFO  | ult-dispatcher-5 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-1-shard-prefix-configuration-shard-config , received role change from Candidate to Leader
2018-03-21 13:22:45,821 | INFO  | d-dispatcher-121 | Shard                            | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-prefix-configuration-shard-operational (Candidate): Starting new election term 21
2018-03-21 13:22:45,858 | INFO  | d-dispatcher-125 | Shard                            | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-prefix-configuration-shard-operational (Candidate) :- Switching from behavior Candidate to Leader, election term: 21
2018-03-21 13:22:45,858 | INFO  | ult-dispatcher-5 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-1-shard-prefix-configuration-shard-operational , received role change from Candidate to Leader
2018-03-21 13:22:45,872 | INFO  | d-dispatcher-125 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-entity-ownership-operational (Candidate): Starting new election term 21
2018-03-21 13:22:45,912 | INFO  | d-dispatcher-145 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | member-1-shard-entity-ownership-operational (Candidate) :- Switching from behavior Candidate to Leader, election term: 21
2018-03-21 13:22:45,921 | INFO  | lt-dispatcher-21 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-1-shard-entity-ownership-operational , received role change from Candidate to Leader

在主机节点二，输出如下：

2018-03-21 13:22:36,286 | INFO  | ult-dispatcher-4 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-2-shard-prefix-configuration-shard-config , received role change from null to Follower
2018-03-21 13:22:36,287 | INFO  | ult-dispatcher-4 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-2-shard-prefix-configuration-shard-operational , received role change from null to Follower
2018-03-21 13:22:36,287 | INFO  | ult-dispatcher-4 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-2-shard-prefix-configuration-shard-config , registered listener akka://opendaylight-cluster-data/user/shardmanager-config
2018-03-21 13:22:36,287 | INFO  | ult-dispatcher-4 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-2-shard-prefix-configuration-shard-operational , registered listener akka://opendaylight-cluster-data/user/shardmanager-operational
2018-03-21 13:22:36,305 | INFO  | rd-dispatcher-32 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | Starting recovery for member-2-shard-entity-ownership-operational with journal batch size 1
2018-03-21 13:22:36,313 | INFO  | rd-dispatcher-38 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | Recovery completed - Switching actor to Follower - Persistence Id =  member-2-shard-entity-ownership-operational Last index in log = -1, snapshotIndex = -1, snapshotTerm = -1, journal-size = 0
2018-03-21 13:22:36,317 | INFO  | ult-dispatcher-2 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-2-shard-entity-ownership-operational , received role change from null to Follower

在主机节点三，输出如下：

2018-03-21 13:22:39,418 | INFO  | ult-dispatcher-6 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-3-shard-prefix-configuration-shard-operational , received role change from null to Follower
2018-03-21 13:22:39,418 | INFO  | ult-dispatcher-6 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-3-shard-prefix-configuration-shard-config , received role change from null to Follower
2018-03-21 13:22:39,418 | INFO  | ult-dispatcher-6 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-3-shard-prefix-configuration-shard-operational , registered listener akka://opendaylight-cluster-data/user/shardmanager-operational
2018-03-21 13:22:39,418 | INFO  | ult-dispatcher-6 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-3-shard-prefix-configuration-shard-config , registered listener akka://opendaylight-cluster-data/user/shardmanager-config
2018-03-21 13:22:39,466 | INFO  | rd-dispatcher-23 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | Starting recovery for member-3-shard-entity-ownership-operational with journal batch size 1
2018-03-21 13:22:39,470 | INFO  | rd-dispatcher-23 | EntityOwnershipShard             | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | Recovery completed - Switching actor to Follower - Persistence Id =  member-3-shard-entity-ownership-operational Last index in log = -1, snapshotIndex = -1, snapshotTerm = -1, journal-size = 0
2018-03-21 13:22:39,473 | INFO  | lt-dispatcher-31 | RoleChangeNotifier               | 120 - org.opendaylight.controller.sal-clustering-commons - 1.6.2 | RoleChangeNotifier for member-3-shard-entity-ownership-operational , received role change from null to Follower

可以看出，第一台Ubuntu主机节点成为Leader，其它两台Ubuntu主机节点成为 Follower ，集群配置成功。但是，从日志也可以看出，对于不同的Shard，存在不同的集群关系。

三、小结

本文详细介绍了Opendaylight Nitrogen集群的搭建指南，后续碰到问题将继续补充。

文章标签：
Ubuntu
Shell
运维
Linux
关键词：
Ubuntu部署
Ubuntu集群
运维集群
运维部署
运维调试
adoryn
目录
相关文章
0utsider
|
26天前
|
Ubuntu Linux 数据安全/隐私保护
Windows11 使用 WSL2部署Ubuntu
在管理员PowerShell中运行命令启用Windows子系统Linux和虚拟机平台，但安装Ubuntu时遇到错误。解决方法是下载NoLsp_fix_WSL2工具，以管理员权限进入其目录，使用工具指向WSL的路径（例如 `C:\windows\system32\wsl.exe`）进行修复，然后能成功打开Ubuntu。
0utsider
34 4
XiaoHHSuperme
|
2月前
|
Kubernetes Ubuntu 应用服务中间件
在Ubuntu22.04 LTS上搭建Kubernetes集群
在Ubuntu22.04.4上安装Kubernetes v1.28.7，步骤超详细
XiaoHHSuperme
311 1
在Ubuntu22.04 LTS上搭建Kubernetes集群
蓝易云
|
3月前
|
Ubuntu Cloud Native 测试技术
百度搜索：蓝易云【云原生之使用Docker部署ubuntu测试环境】
请注意，以上步骤仅是简单的使用Docker部署Ubuntu测试环境的示例。在实际应用中，您可能需要根据测试需求和应用场景进行更多的配置和优化。同时，在退出容器时，容器并未删除，您可以使用 `docker rm <容器名称>`命令来删除容器。在进行测试时，请谨慎操作，并确保对Docker的使用有一定的了解，以避免不必要的问题。
蓝易云
40 2
Aileen_0v0~
|
3月前
|
存储 Ubuntu 网络协议
Ubuntu本地部署Nextcloud并结合内网穿透实现远程访问搭建个人云盘
Ubuntu本地部署Nextcloud并结合内网穿透实现远程访问搭建个人云盘
Aileen_0v0~
125 1
学编程的小程
|
4天前
|
Ubuntu 关系型数据库 MySQL
如何在Ubuntu使用宝塔部署Emlog网站并发布到公网实现任意浏览器访问
如何在Ubuntu使用宝塔部署Emlog网站并发布到公网实现任意浏览器访问
学编程的小程
18 0
didiplus
|
17天前
|
Kubernetes Ubuntu 应用服务中间件
Ubuntu 22.04 利用kubeadm方式部署Kubernetes(v1.28.2版本)
Ubuntu 22.04 利用kubeadm方式部署Kubernetes(v1.28.2版本)
didiplus
80 0
是Yu欸
|
2月前
|
Ubuntu 关系型数据库 MySQL
如何在Ubuntu部署Emlog，并将本地博客发布至公网可远程访问
如何在Ubuntu部署Emlog，并将本地博客发布至公网可远程访问
是Yu欸
37 1
sumith
|
2月前
|
安全 应用服务中间件 开发工具
Ubuntu20安装docker并部署相关漏洞环境
Ubuntu20安装docker并部署相关漏洞环境
sumith
51 0
shuj
|
2月前
|
运维 Java 开发者
深入浅出：使用Docker容器化改善Java应用的部署与运维
在当今快速迭代的软件开发周期中，确保应用的一致性、可移植性与易于管理成为了开发与运维团队面临的重大挑战。本文旨在介绍如何通过Docker容器技术，有效地解决这些问题，特别是针对Java应用。我们将从Docker的基本概念出发，逐步深入到实际操作，展示如何将传统的Java应用容器化，以及这一过程如何帮助简化部署流程、提高应用的可靠性和可伸缩性。不同于常规的技术文章，本文试图以一种更加易于理解和实践的方式，让读者能够快速掌握容器化技术，并将其应用于日常的开发与运维工作中。
shuj
90 0
一只牛博
|
2月前
|
消息中间件 运维 应用服务中间件
容器化运维：构建高可用RabbitMQ集群的Docker Compose指南
容器化运维：构建高可用RabbitMQ集群的Docker Compose指南
一只牛博
159 0

热门文章

最新文章

  • 1
    在阿里云Ubuntu 20.04服务器中搭建一个 Ghost 博客
  • 2
    Ubuntu 22.04 利用kubeadm方式部署Kubernetes(v1.28.2版本)
  • 3
    Ubuntu 中apt 安装MySQL数据库
  • 4
    ubuntu的学习与总结
  • 5
    Ubuntu系统下安装常用软件
  • 6
    Ubuntu桌面图标指南：一文了解如果设置ubuntu 软件图标
  • 7
    Docker从入门到精通：ubuntu系统安装docker
  • 8
    Windows11 使用 WSL2部署Ubuntu
  • 9
    【ubuntu】MobaXtem远程登录ubuntu系统（或虚拟机）
  • 10
    Ubuntu 升级系统版本的注意事项：分享一些在Ubuntu升级系统版本时需要注意的事项和建议
  • 1
    Linux本地部署1Panel现代化运维管理面板并实现公网访问
    65
  • 2
    DataWorks常见问题之dataworks运维中心指定时间“运行到该节点”失败如何解决
    28
  • 3
    运维思考：F5防火墙如何应对潜在威胁？
    17
  • 4
    Hudi的管理与运维
    32
  • 5
    Apache Hudi测试、运维操作万字总结
    72
  • 6
    运维：推荐一款非常专业好用的磁盘空间分析神器TreeSize
    35
  • 7
    运维：推荐23条超级实用的电脑小技巧，小白必备！
    58
  • 8
    运维：Windows 10 快捷键大全，值得收藏
    38
  • 9
    云计算运维常见名词解释
    58
  • 10
    运维工程师的转型与升级：解析35岁半衰期现象及其应对策略
    82

    • 相关课程

    更多
  • 企业运维之弹性计算原理与实践
  • 企业运维之云上网络原理与实践课程
  • 企业级运维之云原生与Kubernetes实战课程
  • 面向运维的 python 脚本速成-1024程序员节创造营公益课
  • Linux企业运维实战 - 入门及常用命令
  • 玩转云上智能运维

    • 相关电子书

    更多
  • 可视化架构运维实践
  • 2021云上架构与运维峰会演讲合集
  • MySQL 技术大全：开发、优化与运维实战

    • 相关实验场景

    更多
  • 使用计算巢企业应用，一键获取专属的Linux服务器管理软件
  • 安装配置Terraform环境
  • 基于ROS快速部署LNMP环境（CentOS 7）
  • 使用物联网平台远程管理运维设备
  • 消息队列RocketMQ版：消费异常运维排查体验
  • 2分钟自动化部署人生模拟器

    • 推荐镜像

    更多
  • ubuntu
  • ubuntu-ports
  • ubuntukylin
    • 下一篇
    阿里云oss简介和使用流程