Ask Your Question

theFog's profile - activity

2015-01-11 22:38:07 -0500 answered a question Icehouse,I haven't command: "nova server-group-create"

The nova client release in icehouse is version 2.17.0 which did not have the support for server groups, its available through the API.

If you want you can install the 2.20.0 version of novaclient on your personal machine as to not impact your installation of openstack. The novaclient 2.20.0 has the built in support for server groups

2014-06-04 10:59:26 -0500 received badge  Famous Question (source)
2014-04-14 04:45:11 -0500 commented answer heat create-stack Forbidden: {"NeutronError": {"message": "Policy doesn't allow create_port to be performed.", "type": "PolicyNotAuthorized", "detail": ""}}

I agree it should work that way, except when only providing the network, the stack creation failed saying uuid was required

2014-04-14 04:43:21 -0500 answered a question heat create-stack Forbidden: {"NeutronError": {"message": "Policy doesn't allow create_port to be performed.", "type": "PolicyNotAuthorized", "detail": ""}}

It should suffice, but unfortunately the stack creation would fail complaining of the missing uuid

2014-04-12 15:35:11 -0500 received badge  Popular Question (source)
2014-04-12 15:35:11 -0500 received badge  Notable Question (source)
2014-04-06 19:07:15 -0500 answered a question heat create-stack Forbidden: {"NeutronError": {"message": "Policy doesn't allow create_port to be performed.", "type": "PolicyNotAuthorized", "detail": ""}}

I was able to resolve it with something like the below template instead. I removed all of the Neutron types and resources as OS::Nova::Server can take the network name and uuid as a parameter

    heat_template_version: 2013-05-23

description: HOT template to deploy two servers to an existing Neutron network.

parameters:
  key_name:
    type: string
    description: Name of keypair to assign to servers
  image:
    type: string
    description: Name of image to use for servers
  flavor:
    type: string
    description: Flavor to use for servers
  net_id:
    type: string
    description: ID of Neutron network into which servers get deployed

resources:
  server1:
    type: OS::Nova::Server
    properties:
      name: Server1
      image: { get_param: image }
      flavor: { get_param: flavor }
      key_name: { get_param: key_name }
      networks:
        - network: { get_param: net_id }
          uuid: { get_param: net_id }

  server2:
    type: OS::Nova::Server
    properties:
      name: Server2
      image: { get_param: image }
      flavor: { get_param: flavor }
      key_name: { get_param: key_name }
      networks:
        - network: { get_param: net_id }
          uuid: { get_param: net_id }

outputs:
  server1_provider_ip:
    description: IP address of server1 in provider network
    value: { get_attr: [ server1, first_address ] }
  server2_provider_ip:
    description: IP address of server2 in provider network
    value: { get_attr: [ server2, first_address ] }
2014-04-06 17:34:23 -0500 received badge  Citizen Patrol
2014-04-05 15:19:12 -0500 asked a question heat create-stack Forbidden: {"NeutronError": {"message": "Policy doesn't allow create_port to be performed.", "type": "PolicyNotAuthorized", "detail": ""}}

When a tenant has multiple subnets available to the tenant it's required to select at least one to provision the machine. I tried using the sample template below to test this and the stack fails to create with a policy error.

    heat_template_version: 2013-05-23

description: HOT template to deploy two servers to an existing Neutron network.

parameters:
  key_name:
    type: string
    description: Name of keypair to assign to servers
  image:
    type: string
    description: Name of image to use for servers
  flavor:
    type: string
    description: Flavor to use for servers
  net_id:
    type: string
    description: ID of Neutron network into which servers get deployed
  subnet_id:
    type: string
    description: ID of Neutron sub network into which servers get deployed

resources:
  server1:
    type: OS::Nova::Server
    properties:
      name: Server1
      image: { get_param: image }
      flavor: { get_param: flavor }
      key_name: { get_param: key_name }
      networks:
        - port: { get_resource: server1_port }

  server1_port:
    type: OS::Neutron::Port
    properties:
      network_id: { get_param: net_id }
      fixed_ips:
        - subnet_id: { get_param: subnet_id }

  server2:
    type: OS::Nova::Server
    properties:
      name: Server2
      image: { get_param: image }
      flavor: { get_param: flavor }
      key_name: { get_param: key_name }
      networks:
        - port: { get_resource: server2_port }

  server2_port:
    type: OS::Neutron::Port
    properties:
      network_id: { get_param: net_id }
      fixed_ips:
        - subnet_id: { get_param: subnet_id }

outputs:
  server1_provider_ip:
    description: IP address of server1 in provider network
    value: { get_attr: [ server1, first_address ] }
  server2_provider_ip:
    description: IP address of server2 in provider network
    value: { get_attr: [ server2, first_address ] }

the event output is

status: create failed
reason: Forbidden: {"NeutronError": {"message": "Policy doesn't allow create_port to be performed.", "type": "PolicyNotAuthorized", "detail": ""}}

even with a single subnet, passing the subnetID causes the same issue. It seems you can only do this if the subnet belongs to the tenant.

has anyone been able to overcome this issue? Is this a bug ?

2013-10-17 15:13:46 -0500 received badge  Good Question (source)
2013-09-16 10:58:40 -0500 received badge  Famous Question (source)
2013-08-28 22:16:17 -0500 received badge  Notable Question (source)
2013-08-01 22:57:57 -0500 received badge  Nice Question (source)
2013-07-31 08:58:10 -0500 received badge  Popular Question (source)
2013-07-29 17:13:43 -0500 received badge  Student (source)
2013-07-28 17:59:06 -0500 asked a question How can I assign more cores to Windows using KVM VCPU with Nova?

When nova through KVM assigns VCPU's or "cores" they show up as physical CPU's inside of Windows rather than a single CPU with X cores. Is there a way to change that behavior to support assigning more than 4C to a WIndows 2008 R2 Standard server ?

The Physical host is running Dual Intel E5-2660 2.2Ghz 8c processors and nova seems to launch the windows servers with a core2duo -smp 8,sockets=8,cores=1, threads=1