+
+
+
diff --git a/view/src/icon_font/iconfont.css b/view/src/icon_font/iconfont.css
new file mode 100644
index 0000000000000000000000000000000000000000..25f57022c6876493d98512ec251fb192051b67b1
--- /dev/null
+++ b/view/src/icon_font/iconfont.css
@@ -0,0 +1,39 @@
+@font-face {
+ font-family: "iconfont"; /* Project id 3657066 */
+ src: url('iconfont.woff2?t=1663574053333') format('woff2'),
+ url('iconfont.woff?t=1663574053333') format('woff'),
+ url('iconfont.ttf?t=1663574053333') format('truetype');
+}
+
+.iconfont {
+ font-family: "iconfont" !important;
+ font-size: 16px;
+ font-style: normal;
+ -webkit-font-smoothing: antialiased;
+ -moz-osx-font-smoothing: grayscale;
+}
+
+.icon-caozuo_zidongliangdu:before {
+ content: "\e670";
+}
+
+.icon-safe:before {
+ content: "\73";
+}
+
+.icon-peihegongzuo:before {
+ content: "\e654";
+}
+
+.icon-peizhi-zhongduanpeizhi:before {
+ content: "\e61b";
+}
+
+.icon-shigongpeihe:before {
+ content: "\e6b9";
+}
+
+.icon-kaixiangjiyong:before {
+ content: "\e627";
+}
+
diff --git a/view/src/icon_font/iconfont.js b/view/src/icon_font/iconfont.js
new file mode 100644
index 0000000000000000000000000000000000000000..f3371a9619e8af871db92ef57163d6cdb6c9cc0c
--- /dev/null
+++ b/view/src/icon_font/iconfont.js
@@ -0,0 +1 @@
+window._iconfont_svg_string_3657066='',function(e){var c=(c=document.getElementsByTagName("script"))[c.length-1],t=c.getAttribute("data-injectcss"),c=c.getAttribute("data-disable-injectsvg");if(!c){var l,i,n,o,a,h=function(c,t){t.parentNode.insertBefore(c,t)};if(t&&!e.__iconfont__svg__cssinject__){e.__iconfont__svg__cssinject__=!0;try{document.write("")}catch(c){console&&console.log(c)}}l=function(){var c,t=document.createElement("div");t.innerHTML=e._iconfont_svg_string_3657066,(t=t.getElementsByTagName("svg")[0])&&(t.setAttribute("aria-hidden","true"),t.style.position="absolute",t.style.width=0,t.style.height=0,t.style.overflow="hidden",t=t,(c=document.body).firstChild?h(t,c.firstChild):c.appendChild(t))},document.addEventListener?~["complete","loaded","interactive"].indexOf(document.readyState)?setTimeout(l,0):(i=function(){document.removeEventListener("DOMContentLoaded",i,!1),l()},document.addEventListener("DOMContentLoaded",i,!1)):document.attachEvent&&(n=l,o=e.document,a=!1,s(),o.onreadystatechange=function(){"complete"==o.readyState&&(o.onreadystatechange=null,d())})}function d(){a||(a=!0,n())}function s(){try{o.documentElement.doScroll("left")}catch(c){return void setTimeout(s,50)}d()}}(window);
\ No newline at end of file
diff --git a/view/src/icon_font/iconfont.json b/view/src/icon_font/iconfont.json
new file mode 100644
index 0000000000000000000000000000000000000000..fbf4a7ad63d4743e3573f3815ee04bae170741a4
--- /dev/null
+++ b/view/src/icon_font/iconfont.json
@@ -0,0 +1,51 @@
+{
+ "id": "3657066",
+ "name": "nestos",
+ "font_family": "iconfont",
+ "css_prefix_text": "icon-",
+ "description": "",
+ "glyphs": [
+ {
+ "icon_id": "1297942",
+ "name": "操作_自动亮度",
+ "font_class": "caozuo_zidongliangdu",
+ "unicode": "e670",
+ "unicode_decimal": 58992
+ },
+ {
+ "icon_id": "7577443",
+ "name": "24gf-shieldCheck",
+ "font_class": "safe",
+ "unicode": "73",
+ "unicode_decimal": 115
+ },
+ {
+ "icon_id": "8651696",
+ "name": "配合工作",
+ "font_class": "peihegongzuo",
+ "unicode": "e654",
+ "unicode_decimal": 58964
+ },
+ {
+ "icon_id": "17523090",
+ "name": "配置-终端配置",
+ "font_class": "peizhi-zhongduanpeizhi",
+ "unicode": "e61b",
+ "unicode_decimal": 58907
+ },
+ {
+ "icon_id": "18468106",
+ "name": "施工配合",
+ "font_class": "shigongpeihe",
+ "unicode": "e6b9",
+ "unicode_decimal": 59065
+ },
+ {
+ "icon_id": "18748999",
+ "name": "开箱即用",
+ "font_class": "kaixiangjiyong",
+ "unicode": "e627",
+ "unicode_decimal": 58919
+ }
+ ]
+}
diff --git a/view/src/icon_font/iconfont.ttf b/view/src/icon_font/iconfont.ttf
new file mode 100644
index 0000000000000000000000000000000000000000..73af3970607058e0bbd749dba1ef8e307a462331
Binary files /dev/null and b/view/src/icon_font/iconfont.ttf differ
diff --git a/view/src/icon_font/iconfont.woff b/view/src/icon_font/iconfont.woff
new file mode 100644
index 0000000000000000000000000000000000000000..b0c58d678a760493b50cba1ea6bcf2895fa9cae4
Binary files /dev/null and b/view/src/icon_font/iconfont.woff differ
diff --git a/view/src/icon_font/iconfont.woff2 b/view/src/icon_font/iconfont.woff2
new file mode 100644
index 0000000000000000000000000000000000000000..a48bf74508293fec76d0bc86c4feaee23f5164d4
Binary files /dev/null and b/view/src/icon_font/iconfont.woff2 differ
diff --git a/view/src/lang/en.js b/view/src/lang/en.js
index a7d6e6f47f5c6ab5915a925ba8ad99066d521d75..162fd9f326e6675ebc96d7c261581425371f09c4 100644
--- a/view/src/lang/en.js
+++ b/view/src/lang/en.js
@@ -11,19 +11,33 @@ export default {
description: 'NestOS cloud base operating system integrates RPM-Ostree support, IGNITION configuration and other technologies, adopts the design idea of dual-system partitioning and atomization update, and uses Nestos-Assembler to quickly integrate and build. It also ADAPTS to K8S, openStack, OKD and other platforms to optimize the bottom noise of container operation. Compared with CENTOS8, the startup speed of container is increased by 30% and the creation speed of container is increased by 60%, which is suitable for the basic operation environment of cloud scenarios mainly based on containerized applications.'
},
minititle: {
+ planIn: 'programme',
+ planOut: 'PROGRAMME',
archIn: 'ARCHITECTURE',
archOut: 'ARCHITECTURE',
+ comIn: 'comparision',
+ comOut: 'COMPARISION',
docIn: 'DOCUMENTATION',
docOut: 'DOCUMENTATION',
resourceIn: 'RESOURCE',
resourceOut: 'RESOURCE',
},
arch: {
- character1: '1. Out of the box container platform: container technology overcomes the user to modify the system configuration, user service system components to rely on conflicts lead to massive cluster service operations difficult problem, at the same time can be quickly installed deployment, according to the service load and convenient real-time extension contraction and node when the operational service smooth migration, is the basis of the most important core cloud native times. Current mainstream general server operating systems need to be installed and deployed before adjusting cloud scenario adaptation. NestOS integrates with mainstream container engines such as iSulad, Docker, Podman, and CLI-O, which can provide users with a lightweight and customized cloud scenario operating system out of the box.',
- character2: '2. Easy to use installation and configuration process: NestOS uses Ignition technology, which can easily complete the installation and configuration of a large number of cluster nodes with the same configuration. Ignition is a distribution-neutral configuration utility for installing and configuring systems and initializing NestOS. The Ignition profile can include configuration for networking, storage, file systems, SystemD units, and user authentication and rights management. During the installation phase, you can manually run the nestos-installer command after booting up the installation image, load the Ignition configuration file, and complete the local installation of NestOS. You can also add the remote Ignition configuration access address to the boot parameters through PXE to realize the network boot installation of a large number of cluster nodes.',
- character3: '3. Secure and reliable package management: NestOS uses RPM-Ostree for package management. Rpm-ostree can be regarded as the combination of RPM and Ostree. On the one hand, Rpm- Ostree provides a way to install and manage software packages based on Rpm, and on the other hand, it provides an update and upgrade of operating system based on Ostree. Each user updates the system as if RPM-ostree commits a "Transaction," ensuring that all updates succeed or fail, and allowing rollback to the pre-update state if the update system encounters an exception.',
- character4: '4. Friendly and controllable automatic update mechanism: NestOS provides automatic update service. As a client of remote update service and RPM-Ostree, NestOS is responsible for detecting whether there is an updated version in the update server and realizing automatic update and reboot of nodes. The service support automatic update agent, user-defined configuration files, and a variety of update strategy, whether the user can automatically update, automatic update strategy options such as configuration, also can be combined with the upper cluster service, will serve the current node load migration after any update, realize the cluster nodes and orderly, ensure the cluster service is not interrupted by the nodes to upgrade. When cluster nodes need to modify their configurations or update the basic environment, release the verified version to the update server. The cluster nodes will be upgraded through the automatic update mechanism.',
- character5: '5. Closely matched dual system partitions: NestOS uses a dual system partition design, with the two partitions set to active and passive modes, respectively, and each performing its duties during system operation. The active partition is responsible for system operation and the passive partition is responsible for system upgrade. Meanwhile, the active partition is set to read-only state during system operation to ensure the integrity and security during NestOS operation. When a new version release of the operating system, a complete file system will be downloaded to passive partition, and restart the system boot from the new version of partition starts, the original passive partition will switch to active partitions, while the active partition before be switch to a passive partitions, the role of two partitions will switch to each other, waiting for the next update system.',
+ title1: 'Out of the box container platform',
+ title2: 'Easy to use installation and configuration process',
+ title3: 'Secure and reliable package management',
+ title4: 'Friendly and controllable automatic update mechanism',
+ title5: 'Closely matched dual system partitions',
+ character1: 'container technology overcomes the user to modify the system configuration, user service system components to rely on conflicts lead to massive cluster service operations difficult problem, at the same time can be quickly installed deployment, according to the service load and convenient real-time extension contraction and node when the operational service smooth migration, is the basis of the most important core cloud native times. Current mainstream general server operating systems need to be installed and deployed before adjusting cloud scenario adaptation. NestOS integrates with mainstream container engines such as iSulad, Docker, Podman, and CLI-O, which can provide users with a lightweight and customized cloud scenario operating system out of the box.',
+ character2: 'NestOS uses Ignition technology, which can easily complete the installation and configuration of a large number of cluster nodes with the same configuration. Ignition is a distribution-neutral configuration utility for installing and configuring systems and initializing NestOS. The Ignition profile can include configuration for networking, storage, file systems, SystemD units, and user authentication and rights management. During the installation phase, you can manually run the nestos-installer command after booting up the installation image, load the Ignition configuration file, and complete the local installation of NestOS. You can also add the remote Ignition configuration access address to the boot parameters through PXE to realize the network boot installation of a large number of cluster nodes.',
+ character3: 'NestOS uses RPM-Ostree for package management. Rpm-ostree can be regarded as the combination of RPM and Ostree. On the one hand, Rpm- Ostree provides a way to install and manage software packages based on Rpm, and on the other hand, it provides an update and upgrade of operating system based on Ostree. Each user updates the system as if RPM-ostree commits a "Transaction," ensuring that all updates succeed or fail, and allowing rollback to the pre-update state if the update system encounters an exception.',
+ character4: 'NestOS provides automatic update service. As a client of remote update service and RPM-Ostree, NestOS is responsible for detecting whether there is an updated version in the update server and realizing automatic update and reboot of nodes. The service support automatic update agent, user-defined configuration files, and a variety of update strategy, whether the user can automatically update, automatic update strategy options such as configuration, also can be combined with the upper cluster service, will serve the current node load migration after any update, realize the cluster nodes and orderly, ensure the cluster service is not interrupted by the nodes to upgrade. When cluster nodes need to modify their configurations or update the basic environment, release the verified version to the update server. The cluster nodes will be upgraded through the automatic update mechanism.',
+ character5: 'NestOS uses a dual system partition design, with the two partitions set to active and passive modes, respectively, and each performing its duties during system operation. The active partition is responsible for system operation and the passive partition is responsible for system upgrade. Meanwhile, the active partition is set to read-only state during system operation to ensure the integrity and security during NestOS operation. When a new version release of the operating system, a complete file system will be downloaded to passive partition, and restart the system boot from the new version of partition starts, the original passive partition will switch to active partitions, while the active partition before be switch to a passive partitions, the role of two partitions will switch to each other, waiting for the next update system.',
+ },
+ compare: {
+ desc: '使用 NestOS beta 版本横向对比 openEuler21.09、openEuler20.03LTS、Centos8 系统运行 iSulad2.0.10 容器引擎性能。',
+ iSulad_x86: 'iSulad(x86_64)测试结果如下:',
+ iSulad_arch: 'iSulad(aarch64)测试结果如下:'
},
resource: {
mirror: 'Mirror',
diff --git a/view/src/lang/zh.js b/view/src/lang/zh.js
index bc85fd8262d15798004715a77ceb4aeff8e0bbc6..174fdad3ebca4d375067a2dab45c1fb55708fae1 100644
--- a/view/src/lang/zh.js
+++ b/view/src/lang/zh.js
@@ -11,19 +11,33 @@ export default {
description: 'NestOS云底座操作系统,集成了rpm-ostree支持、ignition配置等技术,采用双系分区、原子化更新的设计思路,使用nestos-assembler快速集成构建。并针对K8S、openStack、OKD等平台进行适配,优化容器运行底噪,与centos8相比容器启动速度提升了30%,容器创建速度提升了60%,适合作为以容器化应用为主的云场景基础运行环境。'
},
minititle: {
+ planIn: '年度规划',
+ planOut: 'PROGRAMME',
archIn: '架构',
archOut: 'ARCHITECTURE',
+ comIn: '性能对比',
+ comOut: 'COMPARISION',
docIn: '文档',
docOut: 'DOCUMENTATION',
resourceIn: '资源',
resourceOut: 'RESOURCE',
},
arch: {
- character1: '1.开箱即用的容器平台:容器技术克服了用户修改系统配置、用户服务对系统组件依赖冲突等导致大规模集群服务运维困难的问题,同时可以快速的安装部署、根据服务负载方便的实时扩展收缩以及节点运维时服务平滑迁移,是云原生时代最重要的基础核心。当前主流通用服务器操作系统需要安装部署后再次进行云场景适配调整,而 NestOS 集成适配了 iSulad、Docker、Podman 、cri-o 等主流容器引擎,做到开箱即用,可为用户提供一种轻量级、定制化的云场景操作系统。',
- character2: '2.简单易用的安装配置过程:NestOS 采用了 Ignition 技术,可以以相同配置方便地完成大批量集群节点安装配置工作。Ignition 是一个与分发无关的配置实用程序,用于系统的安装和配置并初始化 NestOS。Ignition 配置文件中可以包含对网络、存储、文件系统、systemd 单元和用户鉴权及权限管理等配置。安装阶段,NestOS 既支持引导启动安装镜像后手动运行 nestos-installer 命令,加载 Ignition 配置文件,完成 NestOS 本地安装;也可通过 PXE 方式,在启动引导参数中添加远程 Ignition 配置访问地址,实现大批量集群节点网络引导方式安装。',
- character3: '3.安全可靠的包管理方式:NestOS 使用 rpm-ostree 进行软件包管理,rpm-ostree 可以看成是 rpm 和 ostree 的合体。Rpm-ostree 一方面提供了基于 rpm 的软件包安装管理方式,另一方面提供了基于 ostree 的操作系统更新升级。用户每次对系统更新都像是 rpm-ostree 在提交一次“Transaction”,确保更新过程全部成功或全部失败,并允许在更新系统遇到异常后回滚到更新前状态。',
- character4: '4.友好可控的自动更新机制:NestOS 提供自动更新服务,它作为远程更新服务和 rpm-ostree 的客户端,负责检测更新服务器是否存在更新版本,实现节点自动更新与重新引导。该服务支持自动更新代理、用户自定义配置文件和多种更新策略,用户可对是否自动更新、自动更新策略等选项进行配置,也可与上层集群服务相结合,将当前节点服务负载迁移后再行更新,实现集群节点有序升级,保证集群服务不因节点升级而中断。当集群节点需统一进行配置修改或基础环境更新时,可将修改完毕充分验证后的更新版本发布至更新服务器,集群节点将通过自动更新机制完成统一升级。',
- character5: '5.紧密配合的双系统分区:NestOS 采用双系统分区设计,两个分区分别被设置为主动模式和被动模式,并在系统运行期间各司其职。主动分区负责系统运行,被动分区负责系统升级,同时在系统运行期间主动分区被设置成只读状态,确保 NestOS 运行期间的完整性与安全性。当新版本操作系统发布时,一个完整的文件系统将被下载至被动分区,并在系统重启引导时从新版本分区启动,原来的被动分区将切换为主动分区,而之前的主动分区则被切换为被动分区,两个分区扮演的角色将相互对调,等待下一次系统更新。',
+ title1: '开箱即用的容器平台',
+ title2: '简单易用的安装配置过程',
+ title3: '安全可靠的包管理方式',
+ title4: '友好可控的自动更新机制',
+ title5: '紧密配合的双系统分区',
+ character1: '容器技术克服了用户修改系统配置、用户服务对系统组件依赖冲突等导致大规模集群服务运维困难的问题,同时可以快速的安装部署、根据服务负载方便的实时扩展收缩以及节点运维时服务平滑迁移,是云原生时代最重要的基础核心。当前主流通用服务器操作系统需要安装部署后再次进行云场景适配调整,而 NestOS 集成适配了 iSulad、Docker、Podman 、cri-o 等主流容器引擎,做到开箱即用,可为用户提供一种轻量级、定制化的云场景操作系统。',
+ character2: 'NestOS 采用了 Ignition 技术,可以以相同配置方便地完成大批量集群节点安装置工作。Ignition 是一个与分发无关的配置实用程序,用于系统的安装和配置并初始化 NestOS。Ignition 配置文件中可以包含对网络、存储、文件系统、systemd 单元和用户鉴权及权限管理等配置。安装阶段,NestOS 既支持引导启动安装镜像后手动运行 nestos-installer 命令,加载 Ignition 配置文件,完成 NestOS 本地安装;也可通过 PXE 方式,在启动引导参数中添加远程 Ignition 配置访问地址,实现大批量集群节点网络引导方式安装。',
+ character3: 'NestOS 使用 rpm-ostree 进行软件包管理,rpm-ostree 可以看成是 rpm 和 ostree 的合体。Rpm-ostree 一方面提供了基于 rpm 的软件包安装管理方式,另一方面提供了基于 ostree 的操作系统更新升级。用户每次对系统更新都像是 rpm-ostree 在提交一次“Transaction”,确保更新过程全部成功或全部失败,并允许在更新系统遇到异常后回滚到更新前状态。',
+ character4: 'NestOS 提供自动更新服务,它作为远程更新服务和 rpm-ostree 的客户端,负责检测更新服务器是否存在更新版本,实现节点自动更新与重新引导。该服务支持自动更新代理、用户自定义配置文件和多种更新策略,用户可对是否自动更新、自动更新策略等选项进行配置,也可与上层集群服务相结合,将当前节点服务负载迁移后再行更新,实现集群节点有序升级,保证集群服务不因节点升级而中断。当集群节点需统一进行配置修改或基础环境更新时,可将修改完毕充分验证后的更新版本发布至更新服务器,集群节点将通过自动更新机制完成统一升级。',
+ character5: 'NestOS 采用双系统分区设计,两个分区分别被设置为主动模式和被动模式,并在系统运行期间各司其职。主动分区负责系统运行,被动分区负责系统升级,同时在系统运行期间主动分区被设置成只读状态,确保 NestOS 运行期间的完整性与安全性。当新版本操作系统发布时,一个完整的文件系统将被下载至被动分区,并在系统重启引导时从新版本分区启动,原来的被动分区将切换为主动分区,而之前的主动分区则被切换为被动分区,两个分区扮演的角色将相互对调,等待下一次系统更新。',
+ },
+ compare: {
+ desc: '使用 NestOS beta 版本横向对比 openEuler21.09、openEuler20.03LTS、Centos8 系统运行 iSulad2.0.10 容器引擎性能。',
+ iSulad_x86: 'iSulad(x86_64)测试结果如下:',
+ iSulad_arch: 'iSulad(aarch64)测试结果如下:'
},
resource: {
mirror: '镜像',
diff --git a/view/src/main.js b/view/src/main.js
index 8245978655e5332ec49819e568fb256e05a45157..7f15a1b91b2144ae05b14c826a8bf1391ac048cf 100644
--- a/view/src/main.js
+++ b/view/src/main.js
@@ -7,6 +7,8 @@ import "../node_modules/aos/dist/aos.css";
import ElementPlus from 'element-plus';
import 'element-plus/dist/index.css';
import './styles/main.scss';
+import './icon_font/iconfont.js';
+import './icon_font/iconfont.css';
import '@/utils/rem'
createApp(App).use(router).use(ElementPlus).use(i18n).mount('#app')
diff --git a/view/src/utils/resource.js b/view/src/utils/resource.js
index 32f63c1f8e22d4255d66c6eed099dee0d31089e1..8bdccf7df1eb2c0db35c73e1e627bd37fa5afcb8 100644
--- a/view/src/utils/resource.js
+++ b/view/src/utils/resource.js
@@ -5,11 +5,25 @@
export const docList = [
{
dateTitle: '2022-03-29',
- x86List: ['http://124.126.103.127/nestos20220329/x86_64/nestos-22.03.20220329.dev.0-live.x86_64.iso',
- 'http://124.126.103.127/nestos20220329/x86_64/nestos-22.03.20220329.dev.0-qemu.x86_64.qcow2',
+ x86List: [
+ {
+ name: 'NestOS-22.03 ISO下载',
+ path: 'http://124.126.103.127/nestos20220329/x86_64/nestos-22.03.20220329.dev.0-live.x86_64.iso'
+ },
+ {
+ name: 'NestOS-22.03 QCOW2下载',
+ path: 'http://124.126.103.127/nestos20220329/x86_64/nestos-22.03.20220329.dev.0-qemu.x86_64.qcow2'
+ },
],
- armList: [' http://124.126.103.127/nestos20220329/aarch64/nestos-22.03.20220329.dev.0-live.aarch64.iso',
- ' http://124.126.103.127/nestos20220329/aarch64/nestos-22.03.20220329.dev.0-qemu.aarch64.qcow2',
+ armList: [
+ {
+ name: 'NestOS-22.03 ISO下载',
+ path: 'http://124.126.103.127/nestos20220329/aarch64/nestos-22.03.20220329.dev.0-live.aarch64.iso'
+ },
+ {
+ name: 'NestOS-22.03 QCOW2下载',
+ path: 'http://124.126.103.127/nestos20220329/aarch64/nestos-22.03.20220329.dev.0-qemu.aarch64.qcow2'
+ },
]
},
]
@@ -19,10 +33,15 @@ export const docList = [
*/
export const docFile = [
{
+ title: `resource.file.doc`, // 界面文字
+ link: 'http://124.126.103.127/doc/NestOS.pdf', //下载链接
+ IMG: require('@/assets/resource/illustration-file.png') //背景图小图
+ },
+ /* {
title: `resource.file.doc`,
- link: 'http://124.126.103.127/doc/NestOS.pdf',
- IMG: require('@/assets/resource/illustration-file.png')
- }
+ link: 'http://124.126.103.127/doc/xxx.pdf',
+ IMG: require('@/assets/resource/illustration-xxx.png')
+ } */
]
/*
diff --git a/view/src/views/Architecture.vue b/view/src/views/Architecture.vue
index 364404a93c3342a5b79a4ea9e479c29d8c248d03..443ff69f0610591b757065fb273a0846e21184e4 100644
--- a/view/src/views/Architecture.vue
+++ b/view/src/views/Architecture.vue
@@ -1,13 +1,20 @@