eoscprominence/imc
eoscprominence
Deploy infrastructure across multiple clouds
下载次数: 0状态：社区镜像维护者：eoscprominence仓库类型：镜像最近更新：6 年前
让 AI 帮你使用轩辕镜像？ · 展开查看说明 · 点击收起说明
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具，协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题，请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可：
请先完整阅读并严格遵守以下文档中的全部规则与要求：
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前，不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式，不推荐豆包 AI；Cursor 等编辑器可在对话 @ 该链接，或加入 User Rules。 若 AI 无法访问外链，可 打开说明文档 复制全文粘贴。文档会随站点更新，复制内容可能过期，建议定期检查。
IMC
!https://github.com/prominence-eosc/imc/raw/master/imc.png
Overview
It is frequently assumed that when you're using a cloud you have access to an essentially infinite amount of resources, however this is not always the case. IMC is for situations when you have access to many small clouds (in particular opportunistic access) and you need a tool which can deploy and configure virtual infrastructure across them.
Features include:
- Selection of clouds which meet specified requirements
- e.g. I want to deploy a CentOS 7 VM with at least 8 cores and 32 GB of RAM
- Clouds are ranked based on specified preferences
- e.g. I would prefer my VMs to be deployed on my local private cloud, but if that is full try my national research cloud, but if that is also full then use a public cloud
- If deployment on a cloud fails, another cloud meeting requirements will be automatically tried
- Many types of failures and issues are handled automatically, including:
- deployment failing completely
- contextualization failure
- infrastructure taking too long to deploy or configure
- Couds can be grouped into regions
- Can automatically deploy Ansible hosts with public IP addresses, with only one per cloud, in order to use Ansible for contextualization
IMC uses https://github.com/grycap/im to deploy and configure infrastructure on clouds, including OpenStack, AWS, Azure and Google Compute Platform. It can use either Ansible or Cloud-Init for contextualization. https://www.openpolicyagent.org is used for making decisions about what clouds, VM flavours and images to use.
Configuration
A JSON document in the following form is used to provide static information about known clouds to OPA:
json{ "clouds":{ "cloud1":{...}, "cloud2":{...}, ... "cloudn":{...} } }
Configuration for a single cloud has the form:
json{ "name":"<name>", "region":"<region>", "quotas":{ "cores":i, "instances":j }, "images":{ "<id>":{ "name":"<name>", "architecture":"<arch>", "distribution":"<dist>", "type":"<type>", "version":"<version>" } }, "flavours":{ "<id>":{ "name":"<name>", "cores":i, "memory":j, "tags":{ }, } } }
The image name should be in a form directly useable by IM, for example gce://europe-west2-c/centos-7 (for Google) or ost://<openstack-endpoint>/<id> (for OpenStack). Meta-data is provided for each image to easily enable users to select a standard Linux distribution image at any site, e.g. CentOS 7 or Ubuntu 16.04, without needing to know in advance the image name at each site.
The examples directory has some example configs for different clouds.
Each flavour has an optional tags, which should contain key-value pairs. This can be used to specify additional information about the VM flavour, for example:
json"tags":{ "infiniband":"true" }
Tags can be taken into account with requirements and preferences.
A inter-node network bandwidth capability can also be specified for a cloud, e.g.:
json"network":{ "bandwidth":50 }
This taken into account as a requirement or preference. For the case of a preference, region preferences have priority over network preferences. If you have multiple sites within a region, sites within that region with a network bandwidth larger than the preference will be ranked higher than others.
Deployment
Infrastructure Manager
Deploy Infrastructure Manager following the instructions https://github.com/grycap/im. Alternatively an existing deployment can be used. For testing it is adequate to run the IM Docker container:
docker run -d --name=im -p 127.0.0.1:8899:8899 grycap/im:1.7.4
Open Policy Agent
Deploy Open Policy Agent:
docker run -p 127.0.0.1:8181:8181 -v <directory>:/policies --name=opa -d openpolicyagent/opa:latest run --server /policies
where <directory> should be replaced with the path to the directory on the host containing the policy and data files (i.e. the contents of https://github.com/prominence-eosc/imc/tree/master/policies).
RADL files
IM uses Resource and Application Description Language (RADL) files to describe the infrastructure to be deployed. IMC must be provided with a RADL file, noting that:
${image}will be replaced with the disk image name (essential)${instance}will be replaced with the instance type (essential)${cloud}will be replaced with the name of the cloud${ansible_ip}will be replaced with the public IP address of an appropriate Ansible machine (if needed)${ansible_username}will be replaced with the username of an appropriate Ansible machine (if needed)${ansible_private_key}will be replaced with the private key of an appropriate Ansible machine (if needed)
If the RADL needs to contain a `# IMC
!https://github.com/prominence-eosc/imc/raw/master/imc.png
Overview
It is frequently assumed that when you're using a cloud you have access to an essentially infinite amount of resources, however this is not always the case. IMC is for situations when you have access to many small clouds (in particular opportunistic access) and you need a tool which can deploy and configure virtual infrastructure across them.
Features include:
- Selection of clouds which meet specified requirements
- e.g. I want to deploy a CentOS 7 VM with at least 8 cores and 32 GB of RAM
- Clouds are ranked based on specified preferences
- e.g. I would prefer my VMs to be deployed on my local private cloud, but if that is full try my national research cloud, but if that is also full then use a public cloud
- If deployment on a cloud fails, another cloud meeting requirements will be automatically tried
- Many types of failures and issues are handled automatically, including:
- deployment failing completely
- contextualization failure
- infrastructure taking too long to deploy or configure
- Couds can be grouped into regions
- Can automatically deploy Ansible hosts with public IP addresses, with only one per cloud, in order to use Ansible for contextualization
IMC uses https://github.com/grycap/im to deploy and configure infrastructure on clouds, including OpenStack, AWS, Azure and Google Compute Platform. It can use either Ansible or Cloud-Init for contextualization. https://www.openpolicyagent.org is used for making decisions about what clouds, VM flavours and images to use.
Configuration
A JSON document in the following form is used to provide static information about known clouds to OPA:
json{ "clouds":{ "cloud1":{...}, "cloud2":{...}, ... "cloudn":{...} } }
Configuration for a single cloud has the form:
json{ "name":"<name>", "region":"<region>", "quotas":{ "cores":i, "instances":j }, "images":{ "<id>":{ "name":"<name>", "architecture":"<arch>", "distribution":"<dist>", "type":"<type>", "version":"<version>" } }, "flavours":{ "<id>":{ "name":"<name>", "cores":i, "memory":j, "tags":{ }, } } }
The image name should be in a form directly useable by IM, for example gce://europe-west2-c/centos-7 (for Google) or ost://<openstack-endpoint>/<id> (for OpenStack). Meta-data is provided for each image to easily enable users to select a standard Linux distribution image at any site, e.g. CentOS 7 or Ubuntu 16.04, without needing to know in advance the image name at each site.
The examples directory has some example configs for different clouds.
Each flavour has an optional tags, which should contain key-value pairs. This can be used to specify additional information about the VM flavour, for example:
json"tags":{ "infiniband":"true" }
Tags can be taken into account with requirements and preferences.
A inter-node network bandwidth capability can also be specified for a cloud, e.g.:
json"network":{ "bandwidth":50 }
This taken into account as a requirement or preference. For the case of a preference, region preferences have priority over network preferences. If you have multiple sites within a region, sites within that region with a network bandwidth larger than the preference will be ranked higher than others.
Deployment
Infrastructure Manager
Deploy Infrastructure Manager following the instructions https://github.com/grycap/im. Alternatively an existing deployment can be used. For testing it is adequate to run the IM Docker container:
docker run -d --name=im -p 127.0.0.1:8899:8899 grycap/im:1.7.4
Open Policy Agent
Deploy Open Policy Agent:
docker run -p 127.0.0.1:8181:8181 -v <directory>:/policies --name=opa -d openpolicyagent/opa:latest run --server /policies
where <directory> should be replaced with the path to the directory on the host containing the policy and data files (i.e. the contents of https://github.com/prominence-eosc/imc/tree/master/policies).
RADL files
IM uses Resource and Application Description Language (RADL) files to describe the infrastructure to be deployed. IMC must be provided with a RADL file, noting that:
${image}will be replaced with the disk image name (essential)${instance}will be replaced with the instance type (essential)${cloud}will be replaced with the name of the cloud${ansible_ip}will be replaced with the public IP address of an appropriate Ansible machine (if needed)${ansible_username}will be replaced with the username of an appropriate Ansible machine (if needed)${ansible_private_key}will be replaced with the private key of an appropriate Ansible machine (if needed)
If the RADL needs to contain a character (e.g. for contexutalization) it should be escaped appropriately and written as $.
Usage
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本，请访问 标签列表页面。
DockerHub 原生拉取命令
docker pull eoscprominence/imc:<标签>
镜像拉取常见问题
功能
错误码
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"