Ask Your Question

ccowley's profile - activity

2016-02-01 11:10:53 -0500 received badge  Teacher (source)
2016-01-21 04:30:16 -0500 received badge  Famous Question (source)
2015-12-04 02:54:44 -0500 answered a question Mount multiple cinder volumes to VM via heat

You have given both attachments the same name, so the last one over-rules the first. Try this:

  cinder_relhighiops_volume:                                                        
    type: OS::Cinder::Volume                                                        
    properties:                                                                     
      size: { get_param: volume_size }                                              
      availability_zone: { get_param: availability_zone }                           
      volume_type: relhighiops_type                                                 

  volume_attachment_relhighiops:                                                                
    type: OS::Cinder::VolumeAttachment                                              
    properties:                                                                     
      volume_id: { get_resource: cinder_relhighiops_volume }                        
      instance_uuid: { get_resource: my_instance }                                  

  cinder_highcap_volume:                                                            
    type: OS::Cinder::Volume                                                        
    properties:                                                                     
      size: { get_param: volume_size }                                              
      availability_zone: { get_param: availability_zone }                           
      volume_type: highcap_type                                                     

  volume_attachment_highcap:                                                                
    type: OS::Cinder::VolumeAttachment                                              
    properties:                                                                     
      volume_id: { get_resource: cinder_highcap_volume }                            
      instance_uuid: { get_resource: my_instance }
2015-10-05 05:04:34 -0500 received badge  Famous Question (source)
2015-08-07 10:55:28 -0500 received badge  Notable Question (source)
2015-08-05 19:35:22 -0500 received badge  Popular Question (source)
2015-04-15 09:56:53 -0500 asked a question Using local environment variables in heat template

I want to create an instance that can hit the same API endpoints as I am using create my stack. These endpoints could vary from usage to usage, but they will always be the same as the ones I use to create the instance. As a result I would like to automatically put my credentials (OS_AUTH_URL etc) into my template to inject them into the instance via cloud-init.

How can I do something like:

Parameters :
  os_auth_url :
    default: env[OS_AUTH_URL]
  os_username :
    default: env[OS_AUTH_URL]


Resources :
…
      user_data:
        str_replace:
          "%os_auth_url%": {get_param: os_auth_url }
          "%os_username%": {get_param: os_username }

        template: |
          #cloud-config
          write_files:
          - content: |
              export OS_AUTH_URL=%os_auth_url%
              export OS_USERNAME=%os_username%
            path: /home/cloud/authcreds.rc

At the moment, my solution is to create a template.in that I then pass through sed to create my actual template. Is there a way I can do this natively in Heat?

2014-05-15 05:15:25 -0500 received badge  Notable Question (source)
2014-05-15 05:13:35 -0500 received badge  Editor (source)
2014-05-15 05:12:35 -0500 answered a question Does openstack supports Type1 hypervisor ?

KVM is as much a Type 1 hypervisor as ESX and Hyper-V.

Personally I think they are more a type 1 1/2 hypervisor, but hey. For me a type 1 hypervisor is more along the lines of an IBM system/Z

2014-03-31 02:14:05 -0500 received badge  Famous Question (source)
2014-03-31 02:11:22 -0500 received badge  Enthusiast
2014-03-31 01:56:55 -0500 received badge  Notable Question (source)
2014-03-31 01:24:45 -0500 received badge  Popular Question (source)
2014-03-30 12:57:39 -0500 received badge  Scholar (source)
2014-03-30 12:57:34 -0500 received badge  Supporter (source)
2014-03-29 08:28:09 -0500 commented answer Openstack Neutron stability problems with OpenVSwitch

Sorry should have been more specific, I am on 6.5 and latest RDO already.

I think I have narrowed it down to Glance using up all the disk/network when deploying a large (20GB Windows) instance. MTU config could explain that. I hope to investigate more over the next few weeks.

2014-03-27 05:52:35 -0500 asked a question Openstack Neutron stability problems with OpenVSwitch

I have a fairly simple Openstack setup for a PoC. 2 nodes, both running Nova, and everything else on node 1. It is running CentOS 6 and was set up using RDO. Importantly I am using Neutron for the networking, with GRE tenant networks set up from the RDO docs for an existing network.

Periodically (every few days I reckon) I lose all communication with Openvswitch (and thus my instances). I know it OVS, because I can SSH into node 2, then connect to node 1 via their private network. The most telling thing I see in the logs is this:

unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error)

In addition OVS is using HUGE amounts of CPU (800% on my 16-core boxes), and when I try and do a clean shutdown, it just never happens because it cannot kill ovsdb-server.

I have done some Googling and found some old suggestions based on older Openstack releases where people had OVS/kernel version mismatches. As I am running the versions from RDO I reckon I can discount that (unless Red Hat have made a massive screw up).

Anyone else seen this? have any suggestions?

PS: Do not tell me to recompile Openvswitch, for various reasons that is not happening in the immediate future.

2014-03-14 13:56:21 -0500 received badge  Popular Question (source)
2014-03-13 05:52:17 -0500 received badge  Student (source)
2014-03-12 04:23:30 -0500 asked a question Multiple networks in Openstack Grizzly (Neutron)

I am deploying a PoC/demo on CentOS 6.5. I want to have multiple external networks. The end result should be something like:

http://i1337.photobucket.com/albums/o678/chris_cowley1/networks_zps4aff51f3.png (Desired networks) The 3 networks are come in through a Cisco switch. For various reasons I want to treat them as if they are coming from 3 dumb switches, so VLANs are not an option in this instance.

My understanding is that it should end up looking like: http://i.stack.imgur.com/dtQl5.png (My interpretation of the various networking parts)

Please excuse the bizarre NIC choices, there is a good reason,

When I configure just the external/net0 networks everything works great. I can access the VMs via their external address,different VMs communicate via their internal address, everything works across hosts. So I have eth2 as part of br-ex, physnet2 is mapped to br-ex: - ifcfg-br-ex: http://pastebin.com/kcHcHhkW - ifcfg-eth2: http://pastebin.com/bYQ0298s - ovs_neutron_plugin.ini: http://pastebin.com/FKUadiaz

Now, if I do the same thing with eth0 and eth4 (eth0 -> br-enc -> physnet0 and eth4 -> br-ing - physnet4) I no longer have any external networking.

In this instance my ovs_neutron_plugin.ini is http://pastebin.com/8BCAyPU8 (this).

I create each external network with (modified as necessary):

neutron net-create external --router:external=True \
    --provider:physical_network physnet2 --provider:network_type=flat

Do I have some fundamental misunderstanding of how to use --provider or something?