search

OpenNebula / terraform-provider-opennebula

Terraform provider for OpenNebula
https://www.terraform.io/docs/providers/opennebula/
Mozilla Public License 2.0
67 stars 53 forks source link

Public cloud in opennebula template #186

Closed perrfect closed 1 year ago

perrfect commented 2 years ago

Hello. I need use AWS provider in a opennebula template. But the block of type "PUBLIC_CLOUD" doesn't work in terraform. Іs this option supported?

jaypif commented 2 years ago

HI,

I don't understand your need. AWS provider is AWS provider. It is useful to manage AWS infra and service directly on AWS. It can't be use inside OpenNebula.

Do you mean you want to manage AWS resource via OpenNebula and in that case you need to deploy EC2 instances instead of VM on KVM or vcenter ?

Can you share more details on your need please ?

Thanks

perrfect commented 2 years ago

Hi, thank you for your reply. I want to create hybrid template and to be able to create ec2 instances via Opennebula. For that Opennebula has Amazon EC2 Driver

 public_cloud = {
    AMI          = "ami-030e490"
    HOST         = "5"
    INSTANCETYPE = "t2.micro"
    TYPE         = "ec2"
  }

When I use this driver in template via Opennebula GUI everything is fine, but when i use public_cloud in terraform i get an error.

│ An argument named "public_cloud" is not expected here.

jaypif commented 2 years ago

Hi,

Indeed this is not supported for the moment.

I can't give you an ETA about this yet.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

treywelsh commented 2 years ago

It seems there was some changes around PUBLIC_CLOUD in the documentation: in 6.4 OpenNebula documentation PUBLIC_CLOUD doesn't seems to be documented anymore:

This change already appear from 6.0. Reading 6.0 release note on what happened this seems to be related to the the introduction of edge, provider etc. notions: 

These new edge features in OpenNebula 6.0 include:
...
- A fully-featured command line interface and a modern, slick web interface—FireEdge—to easily manage
  public cloud and edge providers, as well as the seamless provisioning of OpenNebula’s Edge Clusters.
  You can quickly expand your OpenNebula cloud on demand with third-party resources thanks to this
  point and click interface and create an “Edge as a Service” environment in just a few minutes!
- A first set of templates and drivers to expand your OpenNebula cloud using AWS and Equinix Metal resources,
  creating Edge Clusters based on LXC, KVM, and Firecracker.
...

Here is the documentation 6.4 documentation around Edge an cloud provider

Not sure this issue is still relevant with the PUBLIC_CLOUD attribute.

treywelsh commented 2 years ago

@perrfect @frousselet @christian7007 regarding my last comment, and if I'm right, what should we do with this ?

If I have time I'll take a look but any other input is welcomed

treywelsh commented 2 years ago

Some definitions:

A Provider represents a Cloud where resources (hosts, networks or storage) are allocated to implement
a Provision. Usually a Provider includes a zone or region in the target Cloud and an account that
will be used to create the resources needed.

It seems that provider management rely on "meta"-resource document (which has some XML-RPC methods):

I still don't clearly see how all of this works. Anyway, It seems to me that this issue is not relevant anymore.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days.