how to start this about vagrant-cloudstack HOT 7 CLOSED

Hi @ezhang-pivotal

Posting the Vagrantfile you used helps in figuring out what is going wrong, but from the output I suspect you have not specified a correct network UUID

==> default: Fetching name for network with UUID 'network id'

You can either specify a network UUID (something you need to find out in Cloudstack) or a network name (something you also find out in Cloudstack but is easier to remember).
From the output it seems you have set something like

cloudstack.network_id = 'network id'

Where network id should be a UUID of a network in Cloudstack.

from vagrant-cloudstack.

Hi Miguel
Thanks a lot. I'm new to Cloudstack.
---vagrantfile-----

Vagrant.configure("2") do |config|
  # We don't use virtualbox so use dummy
  config.vm.box = "dummy"

  # The username of your bootstrap account
  config.ssh.username = "bootstrap"

  #Path to the SSH key of your bootstrap account
  config.ssh.private_key_path = "~/.ssh/bootstrap.key"

  # Tell Vagrant which version of Chef client to use config.omnibus.chef_version =:latest

  # Tell Vagrant we like to use Berkshelf to resolve our cookbook dependencies config.berkshelf.enabled = true

  # Now configure the Cloudstack parameters
  config.vm.provider :cloudstack do |cloudstack, override|
    cloudstack.host = "cloudstack.cloudprovider.org"
    cloudstack.port = "443"
    cloudstack.scheme = "https"
    cloudstack.api_key = "1234567890qwertyuio"
    cloudstack.secret_key = "1234567890qwertyu"
    cloudstack.template_id = "template id"
    cloudstack.service_offering_id = "offering id"
    cloudstack.network_id = "network id"
    cloudstack.zone_id = "ezone"
    cloudstack.project_id = "ecloud"
    cloudstack.instance_ready_timeout = 300
  end
end

from vagrant-cloudstack.

No worries @ezhang-pivotal, we're here to help you out.

In your Vagrantfile I see that you have not filled in several parameters that are required, namely:

    cloudstack.template_id = "template id"
    cloudstack.service_offering_id = "offering id"
    cloudstack.network_id = "network id"
    cloudstack.zone_id = "ezone"
    cloudstack.project_id = "ecloud"

The vagrant-cloudstack plugin needs you to tell it which zone, project, template, service offering and network to use when creating a VM.
So, you need to have those ready in Cloudstack and then fill in the values in your Vagrantfile.
You can either fill in UUIDs or the names. For the UUIDs you need to use the *_id attributes (just like what you have in your current Vagrantfile). For the names you need to use the respective *_name attributes.

Example Vagrantfile snippet using UUIDs:

    cloudstack.template_id = "12e2209a-cf0f-4aab-ac8b-8c208b25d9aa"
    cloudstack.service_offering_id = "34e2209a-cf0f-4aab-ac8b-8c208b25d9aa"
    cloudstack.network_id = "56e2209a-cf0f-4aab-ac8b-8c208b25d9aa"
    cloudstack.zone_id = "78e2209a-cf0f-4aab-ac8b-8c208b25d9aa"
    cloudstack.project_id = "90e2209a-cf0f-4aab-ac8b-8c208b25d9aa"

(UUIDs are fake, just for reference)

Example Vagrant file snippet using equivalent names:

    cloudstack.template_name = "some_template"
    cloudstack.service_offering_name = "some_service_offering"
    cloudstack.network_name = "some_network"
    cloudstack.zone_name = "ecloud"
    cloudstack.project_name = "ecloud"

Let me know if you run into other difficulties.

from vagrant-cloudstack.

Maybe I have wrong understanding. I still need a Cloudstack to using this? What I'm trying to find is a small cloudstack can run in vagrant

from vagrant-cloudstack.

Yes, you do need a Cloudstack installation to run this against.
Basically, this plugin allows you to use Cloiudstack as a back-end for your Vagrant VMs.

from vagrant-cloudstack.

@ezhang-pivotal can I close this issue?

from vagrant-cloudstack.

Hi Schuberg   Thanks a lot for your help. You can close it now

发送自 Outlook

On Thu, Aug 20, 2015 at 4:27 PM -0700, "Miguel Ferreira" [email protected] wrote:

@ezhang-pivotal can I close this issue?

—
Reply to this email directly or view it on GitHub.

from vagrant-cloudstack.