Ask Your Question

JimZb's profile - activity

2015-07-30 19:10:33 -0500 received badge  Taxonomist
2015-05-24 09:15:22 -0500 received badge  Famous Question (source)
2015-05-20 08:36:34 -0500 received badge  Famous Question (source)
2015-05-20 08:36:34 -0500 received badge  Notable Question (source)
2015-05-20 08:36:34 -0500 received badge  Popular Question (source)
2015-05-08 11:05:44 -0500 asked a question Heat health monitor changes status of members to inactive.

Hello openstack community, I am using a heat template to create an autoscaling group with a load balancer. Currently scale up and down works but the haproxy health monitor associated changes the status of members to inactive therefore I am not getting any replies of the web servers. Each instance takes up to 5 minutes to boot and even though the health monitor delay and timeout have large values, they are still being set to inactive. This is the monitor in the yaml file:

monitor:
  type: OS::Neutron::HealthMonitor
    properties:
      type: HTTP
      delay: 60000
      max_retries: 10
      timeout: 60000
      http_method: GET
      url_path: /myapp

Is there any way to declare a dependency for the Health monitor to start checking after the initialization of at least one member of the auto scaling group? my auto scaling group gets the server template from a file:

resources:
  asg:
    type: OS::Heat::AutoScalingGroup
    properties:
      min_size: 1
      max_size: 2
      resource:
        type: lb_server.yaml
        properties:
          flavor: {get_param: flavor}
          image: {get_param: image}
          key_name: {get_param: key_name}
          network: {get_param: net}
          pool_id: {get_resource: pool}
          metadata: {"metering.stack": {get_param: "OS::stack_id"}}

I am currently looking at adding the depends_on parameter to the health monitor but I cant seem to make it work...

2015-04-20 11:02:54 -0500 received badge  Notable Question (source)
2015-04-16 22:11:16 -0500 received badge  Popular Question (source)
2015-04-16 05:20:55 -0500 asked a question LBaaS Architecture Documentation

I would like to find documentation about how the LBaaS works, what api calls it uses and overall the underlying architecture. I haven't been able to find anything yet explaining how LBaaS works apart from LBaaS Architecture and this LBaaS API and I would like some more details. Something like this would be awesome Ceilometer Architecture

2015-04-14 03:18:30 -0500 received badge  Famous Question (source)
2015-03-29 02:44:44 -0500 received badge  Notable Question (source)
2015-03-29 02:44:44 -0500 received badge  Popular Question (source)
2015-03-25 14:00:23 -0500 commented answer keystone status failed (disabled on boot)

the quickstart guide https://www.rdoproject.org/Quickstart says it not recommended.

2015-03-25 13:28:23 -0500 asked a question keystone status failed (disabled on boot)

Hello, I am using packstack to install openstack on fedora 20. After installation when I run openstack-status all other services are running except from keystone. Note: keystone user-list command works, it displays users fine.

# openstack-status
== Nova services ==
openstack-nova-api:                     active
openstack-nova-cert:                    active
openstack-nova-compute:                 active
openstack-nova-network:                 inactive  (disabled on boot)
openstack-nova-scheduler:               active
openstack-nova-conductor:               active
== Glance services ==
openstack-glance-api:                   active
openstack-glance-registry:              active
== Keystone service ==
openstack-keystone:                     inactive  (disabled on boot)

Following the logs at /var/log/keystone/keystone.conf

2015-03-25 10:57:02.538 10933 ERROR keystone.common.environment.eventlet_server [-] Could not bind to 0.0.0.0:35357
2015-03-25 10:57:02.539 10933 ERROR root [-] Failed to start the admin server
2015-03-25 10:57:02.539 10933 TRACE root Traceback (most recent call last):
2015-03-25 10:57:02.539 10933 TRACE root   File "/usr/bin/keystone-all", line 94, in serve
2015-03-25 10:57:02.539 10933 TRACE root     server.launch_with(launcher)
2015-03-25 10:57:02.539 10933 TRACE root   File "/usr/bin/keystone-all", line 66, in launch_with
2015-03-25 10:57:02.539 10933 TRACE root     self.server.listen()
2015-03-25 10:57:02.539 10933 TRACE root   File "/usr/lib/python2.7/site-packages/keystone/common/environment/eventlet_server.py", line 98, in listen
2015-03-25 10:57:02.539 10933 TRACE root     backlog=backlog)
2015-03-25 10:57:02.539 10933 TRACE root   File "/usr/lib/python2.7/site-packages/eventlet/convenience.py", line 39, in listen
2015-03-25 10:57:02.539 10933 TRACE root     sock.bind(addr)
2015-03-25 10:57:02.539 10933 TRACE root   File "/usr/lib64/python2.7/socket.py", line 224, in meth
2015-03-25 10:57:02.539 10933 TRACE root     return getattr(self._sock,name)(*args)
2015-03-25 10:57:02.539 10933 TRACE root error: [Errno 98] Address already in use
2015-03-25 10:57:02.539 10933 TRACE root 
2015-03-25 10:57:02.540 10933 CRITICAL keystone [-] error: [Errno 98] Address already in use
2015-03-25 10:57:02.540 10933 TRACE keystone Traceback (most recent call last):
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/bin/keystone-all", line 164, in <module>
2015-03-25 10:57:02.540 10933 TRACE keystone     serve(*servers)
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/bin/keystone-all", line 94, in serve
2015-03-25 10:57:02.540 10933 TRACE keystone     server.launch_with(launcher)
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/bin/keystone-all", line 66, in launch_with
2015-03-25 10:57:02.540 10933 TRACE keystone     self.server.listen()
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/lib/python2.7/site-packages/keystone/common/environment/eventlet_server.py", line 98, in listen
2015-03-25 10:57:02.540 10933 TRACE keystone     backlog=backlog)
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/lib/python2.7/site-packages/eventlet/convenience.py", line 39, in listen
2015-03-25 10:57:02.540 10933 TRACE keystone     sock.bind(addr)
2015-03-25 10:57:02.540 10933 TRACE keystone   File "/usr/lib64/python2.7/socket.py", line 224, in meth
2015-03-25 10:57:02.540 10933 TRACE keystone     return getattr(self._sock ...
(more)
2015-02-27 03:25:13 -0500 received badge  Famous Question (source)
2015-02-15 08:24:24 -0500 received badge  Enthusiast
2015-02-09 10:18:43 -0500 received badge  Notable Question (source)
2015-02-07 07:40:54 -0500 received badge  Student (source)
2015-02-07 00:24:03 -0500 received badge  Popular Question (source)
2015-02-06 17:44:12 -0500 received badge  Scholar (source)
2015-02-06 17:43:31 -0500 received badge  Supporter (source)
2015-02-06 17:43:26 -0500 commented answer Fedora 20 (running on Vmware) packstack installation, errors and questions

Thanks again!I'll give it a try!!

2015-02-06 12:58:25 -0500 commented answer Fedora 20 (running on Vmware) packstack installation, errors and questions

Thanks a lot for the reply! So i can configure my system to run packstack multinode without having any extra hardware? Do you happen to have any good installation guide?

2015-02-06 12:56:06 -0500 answered a question Fedora 20 (running on Vmware) packstack installation, errors and questions

Thanks a lot for the reply! So I can configure my system for multinode packstack without having any extra hardware? Do you happen to have any good installation guide?

2015-02-06 08:55:07 -0500 asked a question Fedora 20 (running on Vmware) packstack installation, errors and questions

Hello guys, As the title suggests i am trying to install packstack (openstack-icehouse or juno) on fedora 20 (running on VMWare). The main goal of my project is to create a network with external access where I will be setting up some compute nodes , a load balancer and some alarms in order to create a scaling environment.


The main question I have is whether installing packstack can provide me with these services. I assume that I will be needing neutron, ceilometer, heat and the default services (compute etc.) . Can neutron be set up on a this rig or needs additional nodes as the openstack neutron documentation suggests? Since my fedora VM has a bridged connection with the network, therefore i am assuming that there shouldn't be any implications regarding the virtual environment. Am I on the right track here?


I am new to openstack and my knowledge of fedora is limited. I have also tried Trystack but the ceilometer access is not provided. Thanks!