Re: [Openstack] Unable to launch instance.

Well Vikrant, as you mentioned that you are not using devstack so in that case you need to add the services manually to the compute node (or better try to search for nova.conf), so that you can use console services of nova. Also after adding those service you need to restart the services in all of

[Openstack] [openstack][kilo][compute_driver]

Hello, could you please help me to mention compute driver in kilo? my /etc/nova-compute.conf [DEFAULT] compute_driver=libvirt.LibvirtDriver [libvirt] virt_type = qemu i am getting error like root@kiloctl:~# tail -f /var/log/nova/nova-compute.log 2015-06-08 17:04:53.155 16600 ERROR nova.virt.

Re: [Openstack] Unable to launch instance.

Hi Abhishek, We don't use devstack or any other available ready made packages for installation. As we are using it for production purposes and we have followed official document of openstack Juno. Is it related to network configuration which we done on network node or controller node ? Or relate

Re: [Openstack] Unable to launch instance.

Hi Vikrant, Sorry for the late reply. So you need to add it on that node where DevStack has been installed. If you have not installed devstack then the documentation which you are following is outdated, so you have to search for the updated document where they have included those services. On Sun

[Openstack] Autoscaling group with custom loadbalancer

Hi all, Can we define an autoscaling group which contains ONLY the servers that scaled up and down based on policies. The source of traffic is our own server which works as a loadbalancer. This server is defined as an ordinary server in Heat template outside the autoscaling group definition.

[Openstack] Autoscaling group definition without loadbalancer - Heat template

Hi all, Can we define an autoscaling group which contains ONLY the servers that scaled up and down based on policies. The source of traffic is our own server which works as a loadbalancer. This server is defined as an ordinary server in Heat template outside the autoscaling group definition. I

Re: [Openstack] Autoscaling group definition without loadbalancer - Heat template

The new scaled server sends HTTP request to our loadbalancer to start receiving traffic. Den söndag, 7 juni 2015 21:13 skrev Binan AL Halabi : Hi all, Can we define an autoscaling group which contains ONLY the servers that scaled up and down based on policies. The source of traffi

Re: [Openstack] nova-docker error

Hi Fabrizio, Thanks for your reply. I’ve installed OpenStack Kilo on CentOS 7 with KVM and nova-network (alongside nova, glance, keystone, horizon). And I want to add a Compute node with docker 1.6 hypervisor to the first node (I have nova-compute, nova-network and nova-docker on this server). Y

Re: [Openstack] Swift Atomic Operations

Yes. Write operations are atomically written to disk. Simultaneous reads and writes will not interfere with one another. --John > On Jun 7, 2015, at 5:56 AM, Binan AL Halabi wrote: > > Hi all > > Does Openstack object store provide atomic operations ? > If multiple parties update an objec

Re: [Openstack] Swift Atomic Operations

Hi all Does Openstack object store provide atomic operations ?If multiple parties update an object, will swift guarantees one access at a time  for data integrity? Thank you. Den söndag, 7 juni 2015 14:49 skrev Binan AL Halabi : Hi all Does Openstack object store provide atomic

Re: [Openstack] Adding New Ceilometer Meters

Thanks Romanko, This explain me the entire design of how it should be and it requires lot of work to be done. But why can't ceilometer itself has pollsters for collecting physical Compute nodes related details just like it does for instances. On Fri, Jun 5, 2015 at 1:09 PM, Иван Романько wrote: