Re: [openstack-dev] [octavia] fail to plug vip to amphora

[Ganpat Agarwal]

Hello Yipei,

"*octavia.amphorae.backends.agent.api_server.listener [-] Failed to verify
haproxy file: Command '['haproxy', '-c', '-L', 'NK20KVuD6oi5NrRP7KOVflM*
*3MsQ', '-f',
'/var/lib/octavia/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy.cfg.new']'
returned non-zero exit status 1*"

Verification of haproxy cfg file is failing.

You can create a dummy file from the haproxy template files(jinja2 files)
and verify on any system with haproxy installed.
*haproxy -c -f "filename"*

Regards,
Ganpat

On Wed, Jun 28, 2017 at 3:19 PM, Yipei Niu  wrote:

> Hi, Michael,
>
> Thanks for your help. I have already created a load balancer successfully,
> but failed creating a listener. The detailed errors of amphora-agent and
> syslog in the amphora are as follows.
>
> In amphora-agent.log:
>
> [2017-06-28 08:54:12 +] [1209] [INFO] Starting gunicorn 19.7.0
> [2017-06-28 08:54:13 +] [1209] [DEBUG] Arbiter booted
> [2017-06-28 08:54:13 +] [1209] [INFO] Listening at: http://[::]:9443
> (1209)
> [2017-06-28 08:54:13 +] [1209] [INFO] Using worker: sync
> [2017-06-28 08:54:13 +] [1209] [DEBUG] 1 workers
> [2017-06-28 08:54:13 +] [1816] [INFO] Booting worker with pid: 1816
> [2017-06-28 08:54:15 +] [1816] [DEBUG] POST /0.5/plug/vip/10.0.1.8
> :::192.168.0.12 - - [28/Jun/2017:08:54:59 +] "POST /0.5/plug/vip/
> 10.0.1.8 HTTP/1.1" 202 78 "-" "Octavia HaProxy Rest Client/0.5 (
> https://wiki.openstack.org/wiki/Octavia)"
> [2017-06-28 08:59:18 +] [1816] [DEBUG] PUT
> /0.5/listeners/9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4/
> bca2c985-471a-4477-8217-92fa71d04cb7/haproxy
> :::192.168.0.12 - - [28/Jun/2017:08:59:19 +] "PUT
> /0.5/listeners/9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4/
> bca2c985-471a-4477-8217-92fa71d04cb7/haproxy HTTP/1.1" 400 414 "-"
> "Octavia HaProxy Rest Client/0.5 (https://wiki.openstack.org/wiki/Octavia
> )"
>
> In syslog:
>
> Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
> #
> Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
> -BEGIN SSH HOST KEY FINGERPRINTS-
> Jun 28 08:57:14 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 1024
> SHA256:qDQcKq2Je/CzlpPndccMf0aR0u/KPJEEIAl4RraAgVc
> root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (DSA)
> Jun 28 08:57:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 256
> SHA256:n+5tCCdJwASMaD/kJ6fm0kVNvXDh4aO0si2Uls4MXkI
> root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (ECDSA)
> Jun 28 08:57:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 256
> SHA256:7RWMBOW+QKzeolI6BDSpav9dVZuon58weIQJ9/peVxE
> root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (ED25519)
> Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2: 2048
> SHA256:9z+EcAAUyTENKJRctKCzPslK6Yf4c7s9R8sEflDITIU
> root@amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 (RSA)
> Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
> -END SSH HOST KEY FINGERPRINTS-
> Jun 28 08:57:16 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 ec2:
> #
> Jun 28 08:57:17 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
> cloud-init[2092]: Cloud-init v. 0.7.9 running 'modules:final' at Wed, 28
> Jun 2017 08:57:03 +. Up 713.82 seconds.
> Jun 28 08:57:17 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
> cloud-init[2092]: Cloud-init v. 0.7.9 finished at Wed, 28 Jun 2017 08:57:16
> +. Datasource DataSourceConfigDrive [net,ver=2][source=/dev/sr0].  Up
> 727.30 seconds
> Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
> Started Execute cloud user/final scripts.
> Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
> Reached target Cloud-init target.
> Jun 28 08:57:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
> Startup finished in 52.054s (kernel) + 11min 17.647s (userspace) = 12min
> 9.702s.
> Jun 28 08:59:19 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
> amphora-agent[1209]: 2017-06-28 08:59:19.243 1816 ERROR
> octavia.amphorae.backends.agent.api_server.listener [-] Failed to verify
> haproxy file: Command '['haproxy', '-c', '-L', 'NK20KVuD6oi5NrRP7KOVflM
> 3MsQ', '-f', 
> '/var/lib/octavia/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy.cfg.new']'
> returned non-zero exit status 1
> Jun 28 09:00:11 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
> Starting Cleanup of Temporary Directories...
> Jun 28 09:00:12 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4
> systemd-tmpfiles[3040]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line
> for path "/var/log", ignoring.
> Jun 28 09:00:15 amphora-9ed4f0a5-6b1e-4832-97cc-fb8d1518cbd4 systemd[1]:
> Started Cleanup of Temporary Directories.
>
> Look forward to your valuable comments.
>
> Best regards,
> Yipei
>
> On Tue, Jun 27, 2017 at 2:33 PM, Yipei Niu  wrote:
>
>> Hi, Micheal,
>>
>> Thanks a lot for your help, but I still have one question.
>>
>> In Octavia, once 

Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] devstack install - need help on local.conf settings

[Ganpat Agarwal]

Hi Nidhi,

Try this :

*Set up the network environment on the host so that devstack VMs can access
the external world.*

*sudo bash*
*echo 1 > /proc/sys/net/ipv4/ip_forward*
*echo 1 > /proc/sys/net/ipv4/conf/INTERFACE/proxy_arp*
*iptables -t nat -A POSTROUTING -o INTERFACE -j MASQUERADE*

*These command will make sure that network traffic will be correctly routed
in and out of the devstack VMs.*
*The ip_forward and proxy_arp changes will be reset when the machice
reboots. You can make these changes permanent by editing /etc/sysctl.conf
and adding the following lines:*

*net.ipv4.conf.INTERFACE.proxy_arp = 1*
*net.ipv4.ip_forward = 1*

*Replace INTERFACE with ethernet interface of your virtual box.*

Hope it will work as it works always for me.

Regards,
Ganpat

On Fri, Jun 2, 2017 at 3:01 PM, nidhi.h...@wipro.com 
wrote:

> Hello all,
>
>
>
> I am using http://paste.openstack.org/show/595339/ as my local.conf.
>
>
>
> *I wanted to understand :- Which interface should we put as value in *
>
> *PUBLIC_INTERFACE in local.conf.*
>
>
>
>
>
> *Reason why I am asking this is,*
>
>
>
> Once, I installed OpenStack using DevStack, on my linux VM on
>
> VirtualBox - I used PUBLIC_INTERFACE value as eth0
>
> and
>
> I configured only one network adapter on VM in NAT mode.
>
>
>
> Later on I faced lot of networking problems in that OpenStack VM.
>
> Internet wasn’t accessible suddenly and many other probs.
>
>
>
> I debugged and somehow found eth0 was added in
>
> One ovs-bridge and if I remove eth0 from that bridge -
>
> only then internet in my VM used to work well.
>
>
>
> Then I doubted PUBLIC_INTERFACE value in local.conf
>
> is something I should setup correctly..
>
>
>
> Could not find much help on this from google.
>
>
>
> Can someone please enlighten?
>
>
>
> Thanks
>
> Nidhi
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *From:* Nidhi Mittal Hada (Product Engineering Service)
> *Sent:* Wednesday, January 18, 2017 3:49 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing
> problem in devstack install - No Network found for private
>
>
>
> Hi Andreas,
>
>
>
> As in between you suggested to try with default devstack
>
> neutron config params. I tried that i set no config option
>
> for neutron part all default.
>
>
>
> This local.conf is working well..
>
>
>
> for others who are facing problem pasting working local.conf here
>
> http://paste.openstack.org/show/595339/
>
>
>
> Attaching too.
>
>
>
> Thanks
>
> Nidhi
>
>
>
>
>
>
>
>
> --
>
> *From:* Nidhi Mittal Hada (Product Engineering Service)
> *Sent:* Wednesday, January 18, 2017 2:44 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing
> problem in devstack install - No Network found for private
>
>
>
> Andreas,
>
>
>
> I require nothing specific from neutron side.
>
> Just a basic working setup from neutron side
>
> because my work is mostly on storage side of
>
> OpenStack.
>
>
>
> Can you please suggest a working configuration
>
> if  tried recently.
>
>
>
> Thanks
>
> nidhi
>
>
> --
>
> *From:* Nidhi Mittal Hada (Product Engineering Service)
> *Sent:* Wednesday, January 18, 2017 2:35:13 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* Re: [openstack-dev] [OpenStack-Dev][DevStack][Neutron] facing
> problem in devstack install - No Network found for private
>
>
>
> HI Andreas,
>
>
>
> Thanks for your reply.
>
>
>
> I have no specific reason for using this network configuration in
> local.conf.
>
> I have only basic knowledge of these config options even.
>
> This local.conf network configurations used to work well with earlier
>
> devstack openstack versions. So i did not change it..
>
> Just this time its creating trouble.
>
>
>
> I have not created any ovs bridge manually  before running devstack.
>
> just created this local.conf and ran ./stack.sh in devstack folder.
>
>
>
> Can you please suggest changes if i have not created ovs-bridge manually.
>
>
>
> *At present my settings are - from local.conf - for reference - *
>
> FIXED_RANGE=10.11.12.0/24
>
> NETWORK_GATEWAY=10.11.12.1
>
> FIXED_NETWORK_SIZE=256
>
>
>
> FLOATING_RANGE=10.0.2.0/24
>
> Q_FLOATING_ALLOCATION_POOL=start=10.0.2.104,end=10.0.2.111
>
> PUBLIC_NETWORK_GATEWAY=10.0.2.1
>
> HOST_IP=10.0.2.15
>
>
>
> PUBLIC_INTERFACE=eth0
>
>
>
> Q_USE_SECGROUP=True
>
> ENABLE_TENANT_VLANS=True
>
> TENANT_VLAN_RANGE=1000:1999
>
> PHYSICAL_NETWORK=default
>
> OVS_PHYSICAL_BRIDGE=br-ex
>
>
>
>
>
> Q_USE_PROVIDER_NETWORKING=True
>
> Q_L3_ENABLED=False
>
>
>
> PROVIDER_SUBNET_NAME="provider_net"
>
> PROVIDER_NETWORK_TYPE="vlan"
>
> SEGMENTATION_ID=2010
>
>
>
>
>
>
>
>
>
>
>
> Thanks
>
> Nidhi
>
>
>
>
> --
>
> *From:* Andreas Scheuring 
> *Sent:* Wednesday, January 18, 2017 1:09:17 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* Re: 

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

[Ganpat Agarwal]

Thanks a lot Michael.

Recreating the amphora image with Ubuntu Trusty solved the issue for me.

We are planning to add octavia on our *ansible* managed cloud, but could
not find any concrete documentation.Will give it a try.

Regards,
Ganpat



On Wed, Nov 16, 2016 at 10:20 PM, Michael Johnson <johnso...@gmail.com>
wrote:

> Hi Ganpat,
>
> FYI, we are on freenode IRC: #openstack-lbaas if you would like to
> chat interactively.
>
> So, I see the amp is expecting systemd, which probably means you are
> using a "master" version of diskimage-builder with a stable/newton
> version of Octavia.  On November 2nd, they switched diskimage-builder
> to use a xenial Ubuntu image by default.  This patch just merged on
> Octavia master to support that change:
> https://review.openstack.org/396438
>
> I think you have two options:
> 1. Set the environment variable DIB_RELEASE=trusty and recreate the
> amphora image[1].
> 2. Install the stable/newton version of diskimage-builder and recreate
> the amphora image.
>
> For option one I have pasted a script I use to rebuild the image with
> Ubuntu trusty.
> Note, this script will delete your current image in glance and expects
> the octavia repository to be located in /opt/stack/octavia, so please
> update it as needed.
>
> Michael
>
> [1] https://gist.github.com/michjohn/a7cd582fc19e0b4bc894eea6249829f9
>
> On Wed, Nov 16, 2016 at 8:25 AM, Ganpat Agarwal
> <gans.develo...@gmail.com> wrote:
> > Here are the steps i followed
> >
> > 1. Created a LB
> >
> > stack@devstack-openstack:~/devstack$ neutron lbaas-loadbalancer-list
> > +--+--+-
> +-+--+
> > | id   | name | vip_address |
> > provisioning_status | provider |
> > +--+--+-
> +-+--+
> > | 1ffcfe97-99a3-47c1-9df1-63bac71d9e04 | lb1  | 10.0.0.10   |
> PENDING_CREATE
> > | octavia  |
> > +--+--+-
> +-+--+
> >
> > 2. List amphora instance
> > stack@devstack-openstack:~/devstack$ nova list
> > +--+
> --+++---
> --+-
> -+
> > | ID   | Name
> > | Status | Task State | Power State | Networks
> > |
> > +--+
> --+++---
> --+-
> -+
> > | 89dc06b7-00a9-456f-abc9-50f14e1bc78b |
> > amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd | ACTIVE | -  |
> Running
> > | lb-mgmt-net=192.168.0.6; private=10.0.0.11,
> > fdbc:aa5f:a6ae:0:f816:3eff:fe0b:86d7 |
> > +--+
> --+++---
> --+-
> -+
> >
> > 3. able to ssh on lb-mgmt-ip , 192.168.0.6
> >
> > Network config
> >
> > ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ ip a
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
> > default qlen 1
> > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> > inet 127.0.0.1/8 scope host lo
> >valid_lft forever preferred_lft forever
> > inet6 ::1/128 scope host
> >valid_lft forever preferred_lft forever
> > 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast
> state
> > UP group default qlen 1000
> > link/ether fa:16:3e:02:a7:50 brd ff:ff:ff:ff:ff:ff
> > inet 192.168.0.6/24 brd 192.168.0.255 scope global ens3
> >valid_lft forever preferred_lft forever
> > inet6 fe80::f816:3eff:fe02:a750/64 scope link
> >valid_lft forever preferred_lft forever
> > 3: ens6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default
> > qlen 1000
> >
> >
> > 4. No amphora agent running
> >
> > ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ sudo service
> > amphora-agent status
> > ● amphora-agent.service
> >Loaded: not-found (Reason: No such file or directory)
> >Active: inactive (dead)
> >
> > ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ sudo service
>

Re: [openstack-dev] 答复: [neutron][lbaasv2][octavia] Not able to create loadbalancer

[Ganpat Agarwal]

Here are the steps i followed

1. Created a LB

stack@devstack-openstack:~/devstack$ neutron lbaas-loadbalancer-list
+--+--+-+-+--+
| id   | name | vip_address |
provisioning_status | provider |
+--+--+-+-+--+
| 1ffcfe97-99a3-47c1-9df1-63bac71d9e04 | lb1  | 10.0.0.10   |
PENDING_CREATE  | octavia  |
+--+--+-+-+--+

2. List amphora instance
stack@devstack-openstack:~/devstack$ nova list
+--+--+++-+--+
| ID   | Name
  | Status | Task State | Power State | Networks
  |
+--+--+++-+--+
| 89dc06b7-00a9-456f-abc9-50f14e1bc78b |
amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd | ACTIVE | -  |
Running | lb-mgmt-net=192.168.0.6; private=10.0.0.11,
fdbc:aa5f:a6ae:0:f816:3eff:fe0b:86d7 |
+--+--+++-+--+

3. able to ssh on lb-mgmt-ip , 192.168.0.6

Network config

ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state
UP group default qlen 1000
link/ether fa:16:3e:02:a7:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.6/24 brd 192.168.0.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe02:a750/64 scope link
   valid_lft forever preferred_lft forever
3: ens6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000


4. No amphora agent running

ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ sudo service
amphora-agent status
● amphora-agent.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

ubuntu@amphora-41ac5ea5-c4f6-4b13-add5-edf4ac4ae0dd:~$ sudo service
amphora-agent start
Failed to start amphora-agent.service: Unit amphora-agent.service not found.


How to proceed from here?


On Wed, Nov 16, 2016 at 6:04 PM, 洪 赵 <hong.z...@live.com> wrote:

> After the amphora vm was created, the Octavia worker tried to plug VIP to
> the amphora  vm, but failed. It could not connect to the amphora agent. You
> may ssh to the vm and check if the networks and ip addresses are correctly
> set.
>
>
>
> Good luck.
>
> -hzhao
>
>
>
> *发件人: *Ganpat Agarwal <gans.develo...@gmail.com>
> *发送时间: *2016年11月16日 14:40
> *收件人: *OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> *主题: *[openstack-dev] [neutron][lbaasv2][octavia] Not able to create
> loadbalancer
>
>
> Hi All,
>
> I am using devstack stable/newton branch and have deployed octavia for
> neutron-lbaasv2.
>
> Here is my local.conf
>
> [[local|localrc]]
> HOST_IP=10.0.2.15
> DATABASE_PASSWORD=$ADMIN_PASSWORD
> MYSQL_PASSWORD=$ADMIN_PASSWORD
> RABBIT_PASSWORD=$ADMIN_PASSWORD
> SERVICE_PASSWORD=$ADMIN_PASSWORD
> SERVICE_TOKEN=tokentoken
> DEST=/opt/stack
>
> # Disable Nova Network and enable Neutron
> disable_service n-net
> enable_service q-svc
> enable_service q-agt
> enable_service q-dhcp
> enable_service q-l3
> enable_service q-meta
>
> # Enable LBaaS v2
> enable_plugin neutron-lbaas https://git.openstack.org/
> openstack/neutron-lbaas stable/newton
> enable_plugin octavia https://git.openstack.org/openstack/octavia
> stable/newton
> enable_service q-lbaasv2
> enable_service octavia
> enable_service o-cw
> enable_service o-hm
> enable_service o-hk
> enable_service o-api
>
> # Neutron options
> Q_USE_SECGROUP=True
> FLOATING_RANGE="172.18.161.0/24"
> FIXED_RANGE="10.0.0.0/24"
> Q_FLOATING_ALLOCATION_POOL=start=172.18.161.250,end=172.18.161.254
> PUBLIC_NETWORK_GATEWAY="172.18.161.1"
> PUBLIC_INTERFACE=eth0
>
> LOG=True
> VERB

[openstack-dev] [neutron][lbaasv2][octavia] Not able to create loadbalancer

[Ganpat Agarwal]

Hi All,

I am using devstack stable/newton branch and have deployed octavia for
neutron-lbaasv2.

Here is my local.conf

[[local|localrc]]
HOST_IP=10.0.2.15
DATABASE_PASSWORD=$ADMIN_PASSWORD
MYSQL_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
SERVICE_TOKEN=tokentoken
DEST=/opt/stack

# Disable Nova Network and enable Neutron
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta

# Enable LBaaS v2
enable_plugin neutron-lbaas
https://git.openstack.org/openstack/neutron-lbaas stable/newton
enable_plugin octavia https://git.openstack.org/openstack/octavia
stable/newton
enable_service q-lbaasv2
enable_service octavia
enable_service o-cw
enable_service o-hm
enable_service o-hk
enable_service o-api

# Neutron options
Q_USE_SECGROUP=True
FLOATING_RANGE="172.18.161.0/24"
FIXED_RANGE="10.0.0.0/24"
Q_FLOATING_ALLOCATION_POOL=start=172.18.161.250,end=172.18.161.254
PUBLIC_NETWORK_GATEWAY="172.18.161.1"
PUBLIC_INTERFACE=eth0

LOG=True
VERBOSE=True
LOGFILE=$DEST/logs/stack.sh.log
LOGDAYS=1
SCREEN_LOGDIR=$DEST/logs/screen
SYSLOG=True
SYSLOG_HOST=$HOST_IP
SYSLOG_PORT=516
RECLONE=yes


While creating loadbalancer, i am getting error in octavia worker

2016-11-16 06:13:08.264 4115 INFO octavia.controller.queue.consumer [-]
Starting consumer...
2016-11-16 06:14:58.507 4115 INFO octavia.controller.queue.endpoint [-]
Creating load balancer '51082942-b348-4900-bde9-6d617dba8f99'...
2016-11-16 06:14:59.204 4115 INFO
octavia.controller.worker.tasks.database_tasks [-] Created Amphora in DB
with id 93e28edd-71ee-4448-bc70-b0424dbd64f5
2016-11-16 06:14:59.334 4115 INFO octavia.certificates.generator.local [-]
Signing a certificate request using OpenSSL locally.
2016-11-16 06:14:59.336 4115 INFO octavia.certificates.generator.local [-]
Using CA Certificate from config.
2016-11-16 06:14:59.336 4115 INFO octavia.certificates.generator.local [-]
Using CA Private Key from config.
2016-11-16 06:14:59.337 4115 INFO octavia.certificates.generator.local [-]
Using CA Private Key Passphrase from config.
2016-11-16 06:15:15.085 4115 INFO
octavia.controller.worker.tasks.database_tasks [-] Mark ALLOCATED in DB for
amphora: 93e28edd-71ee-4448-bc70-b0424dbd64f5 with compute id
f339b48d-1445-47e0-950b-ee69c2add81f for load balancer:
51082942-b348-4900-bde9-6d617dba8f99
2016-11-16 06:15:15.208 4115 INFO
octavia.network.drivers.neutron.allowed_address_pairs [-] Port
ac27cbb8-078d-47fd-824c-e95b0ebff392 already exists. Nothing to be done.
2016-11-16 06:15:39.708 4115 WARNING
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to
instance. Retrying.
2016-11-16 06:15:47.712 4115 WARNING
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to
instance. Retrying.

several 100 lines with same message

2016-11-16 06:24:29.310 4115 WARNING
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to
instance. Retrying.
^[2016-11-16 06:24:34.316 4115 WARNING
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to
instance. Retrying.
2016-11-16 06:24:39.317 4115 ERROR
octavia.amphorae.drivers.haproxy.rest_api_driver [-] Connection retries
(currently set to 100) exhausted.  The amphora is unavailable.
2016-11-16 06:24:39.327 4115 WARNING
octavia.controller.worker.controller_worker [-] Task
'octavia.controller.worker.tasks.amphora_driver_tasks.AmphoraePostVIPPlug'
(19f29ca9-3e7f-4629-b976-b4d24539d8ed) transitioned into state 'FAILURE'
from state 'RUNNING'
33 predecessors (most recent first):
  Atom
'octavia.controller.worker.tasks.network_tasks.GetAmphoraeNetworkConfigs'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'loadbalancer':
},
'provides': {u'93e28edd-71ee-4448-bc70-b0424dbd64f5':
}}
  |__Atom 'reload-lb-after-plug-vip' {'intention': 'EXECUTE', 'state':
'SUCCESS', 'requires': {'loadbalancer_id':
u'51082942-b348-4900-bde9-6d617dba8f99'}, 'provides':
}
 |__Atom
'octavia.controller.worker.tasks.database_tasks.UpdateAmphoraVIPData'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'amps_data':
[]},
'provides': None}
|__Atom 'octavia.controller.worker.tasks.network_tasks.PlugVIP'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'loadbalancer':
},
'provides': []}
   |__Atom
'octavia.controller.worker.tasks.database_tasks.UpdateVIPAfterAllocation'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'vip':
,
'loadbalancer_id': u'51082942-b348-4900-bde9-6d617dba8f99'}, 'provides':
}
  |__Atom
'octavia.controller.worker.tasks.network_tasks.AllocateVIP' {'intention':
'EXECUTE', 'state': 'SUCCESS', 'requires': {'loadbalancer':
},
'provides': }
 |__Flow 'octavia-new-loadbalancer-net-subflow'
|__Atom
'octavia-post-loadbalancer-amp_association-subflow-octavia-post-loadbalancer-amp_association-subflow-reload-lb-after-amp-assoc'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 

Re: [openstack-dev] [devstack][mitaka] Unable stack.sh on ubuntu 14.04.5LTS (TypeError: 'Documentation' object is not iterable)

[Ganpat Agarwal]

Hi,

Your logs says that it failed during installation of "rcssmin" package.

Did you tried installing it manually, or removing it completely and
re-installing?

It may be because of version conflict across the dependencies for this
package.

Regards,
Ganpat

On Tue, Nov 1, 2016 at 8:10 PM, Srikanth Vavilapalli <
srikanth.vavilapa...@ericsson.com> wrote:

> Hi
>
>
>
> One quick update on this issue:
>
>
>
> For some reason I see this issue only with devstack mitaka on vagrant VM
> spawned using virtualbox provider(Ubuntu/trusty64 box). It used to work
> before though…
>
>
>
> On the same vagrant VM, I installed devstack Liberty which is working
> without any issues. Also I tried devstack mitaka on vagrant VM spawned
> using libvirt provider and interestingly that is also working.
>
>
>
> Not sure what the issue with vagrant virtualbox VM…
>
>
>
> Thanks
>
> Srikanth
>
>
>
> *From:* Srikanth Vavilapalli [mailto:srikanth.vavilapa...@ericsson.com]
> *Sent:* Saturday, October 29, 2016 3:03 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [devstack][mitaka] Unable stack.sh on ubuntu
> 14.04.5LTS (TypeError: 'Documentation' object is not iterable)
>
>
>
> Hi
>
>
>
> I am consistently getting the following error when I run stack.sh on my
> vagrant VM with Ubuntu 14.04.5 OS. I tried to upgrade setuptools and
> distribute, but none of them were able to solve this error. Can you plz
> help me how to resolve this error. Plz let me know if u need further data
> here…
>
>
>
> Thanks
>
> Srikanth
>
>
>
>
>
>
>
> 2016-10-29 21:52:27.289 | Configuring Horizon
>
> +./stack.sh:main:1057  configure_horizon
>
> +lib/horizon:configure_horizon:79  setup_develop
> /opt/stack/horizon
>
> +inc/python:setup_develop:271  local
> project_dir=/opt/stack/horizon
>
> +inc/python:setup_develop:272  local extras=
>
> +inc/python:setup_develop:273  
> _setup_package_with_constraints_edit
> /opt/stack/horizon -e
>
> +inc/python:_setup_package_with_constraints_edit:303  local
> project_dir=/opt/stack/horizon
>
> +inc/python:_setup_package_with_constraints_edit:304  local flags=-e
>
> +inc/python:_setup_package_with_constraints_edit:305  local extras=
>
> +inc/python:_setup_package_with_constraints_edit:307  '[' -n
> /opt/stack/requirements ']'
>
> +inc/python:_setup_package_with_constraints_edit:309  local name
>
> ++inc/python:_setup_package_with_constraints_edit:310  awk '/^name.*=/
> {print $3}' /opt/stack/horizon/setup.cfg
>
> +inc/python:_setup_package_with_constraints_edit:310  name=horizon
>
> +inc/python:_setup_package_with_constraints_edit:312
>  /opt/stack/requirements/.venv/bin/edit-constraints
> /opt/stack/requirements/upper-constraints.txt -- horizon '-e
> file:///opt/stack/horizon#egg=horizon'
>
> +inc/python:_setup_package_with_constraints_edit:316  setup_package
> /opt/stack/horizon -e
>
> +inc/python:setup_package:332  local
> project_dir=/opt/stack/horizon
>
> +inc/python:setup_package:333  local flags=-e
>
> +inc/python:setup_package:334  local extras=
>
> +inc/python:setup_package:338  [[ -n -e ]]
>
> +inc/python:setup_package:338  [[ -z '' ]]
>
> +inc/python:setup_package:338  [[ ! -e =~ ^-.* ]]
>
> +inc/python:setup_package:343  [[ ! -z '' ]]
>
> +inc/python:setup_package:347  pip_install -e
> /opt/stack/horizon
>
> +inc/python:pip_install:84 local xtrace result
>
> ++inc/python:pip_install:85 set +o
>
> ++inc/python:pip_install:85 grep xtrace
>
> +inc/python:pip_install:85 xtrace='set -o xtrace'
>
> +inc/python:pip_install:86 set +o xtrace
>
> +inc/python:pip_install:155sudo -H http_proxy=
> https_proxy= no_proxy= PIP_FIND_LINKS= SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite
> /usr/local/bin/pip2.7 install -c /opt/stack/requirements/upper-constraints.txt
> --upgrade -e /opt/stack/horizon
>
> Ignoring dnspython3: markers u"python_version=='3.4'" don't match your
> environment
>
> Obtaining file:///opt/stack/horizon
>
> Obtaining horizon from file:///opt/stack/horizon#egg=horizon (from -c
> /opt/stack/requirements/upper-constraints.txt (line 1))
>
> Requirement already up-to-date: Babel===2.2.0 in
> /usr/local/lib/python2.7/dist-packages (from -c
> /opt/stack/requirements/upper-constraints.txt (line 3))
>
> …
>
> Requirement already up-to-date: python-openstackclient===2.3.0 in
> /usr/local/lib/python2.7/dist-packages (from -c
> /opt/stack/requirements/upper-constraints.txt (line 305))
>
> Requirement already up-to-date: python-swiftclient===3.0.0 in
> /usr/local/lib/python2.7/dist-packages (from -c
> /opt/stack/requirements/upper-constraints.txt (line 313))
>
> Requirement already up-to-date: pytz===2015.7 in
> /usr/local/lib/python2.7/dist-packages (from -c
> /opt/stack/requirements/upper-constraints.txt (line 316))
>
> Collecting rcssmin===1.0.6 

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

[Ganpat Agarwal]

That's correct.

We can have meters only for those things which we can measure like cpu,
memory etc.

If we want to keep a count of instance creation and deletion, you will need
to monitor the events and look for specific event types like
compute.instance.create.end or compute.instance.delete.end.

On Wed, Nov 2, 2016 at 2:42 AM, gordon chung  wrote:

>
>
> On 01/11/16 05:30 AM, Raghunath D wrote:
> > My requirement is to get sample/counter with "instance" name ,with
> > event_type *compute.instance.**
>
> we don't build instance meter anymore because it's not a meter as it's
> not measuring anything.
>
> --
> gord
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

[Ganpat Agarwal]

Hi Raghunath,

I am not able to understand your use case for compute.instance.* events.

You are trying to catch the instance start and end events OR you want the
samples related with these events?

Regards,
Ganpat

On Wed, Oct 26, 2016 at 6:00 PM, Raghunath D <raghunat...@tcs.com> wrote:

> Hi Ganpat/Gord,
>
> Callback for compute.instance.create.end events under 
> ceilometer.compute.notifications
> should be invoked for those notification events on the nova exchange using
> the notifications.info topic.
> But this is not happening,we can see events related to them and can
> receive events over kafka.
>
> I can see from logs which print my debug print during the loading of
> notification plugin.
> "2016-10-26 03:46:32.010 34977 INFO ceilometer.compute.notifications.instance
> [req-1ad3d5c9-5eab-404d-9fbe-f1605e93691f - - - - -] Check
> ComputeInstanceNotificationBase notification:"
>
> Do we need to change any thing in the configuration file of ceilometer or
> nova to achive this.
> It would be great help for me if this is fixed.
>
> With Best Regards
> Raghunath Dudyala
> Tata Consultancy Services Limited
> Mailto: raghunat...@tcs.com
> Website: http://www.tcs.com
> 
> Experience certainty. IT Services
> Business Solutions
> Consulting
> 
>
>
> -Ganpat Agarwal <gans.develo...@gmail.com> wrote: -
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> From: Ganpat Agarwal <gans.develo...@gmail.com>
> Date: 10/25/2016 09:32PM
>
> Subject: Re: [openstack-dev] [Ceilometer]: Instance creation and deletion
> metrics in ceilometer !
>
> Hi Raghunath,
>
> You can look at this file for details of meters related with
> compute.instance.*
>
> ceilometer/meter/data/meters.yaml
>
> Additionally, you can look at this link for compute meters documentation
>
> http://docs.openstack.org/admin-guide/telemetry-measurements.html
>
>
> Also, have a look at "Meters definitions" section on this link
>
> http://docs.openstack.org/admin-guide/telemetry-data-
> collection.html#meter-definitions
>
> Regards,
> Ganpat
>
>
> On Tue, Oct 25, 2016 at 5:45 PM, Raghunath D <raghunat...@tcs.com> wrote:
>
>> Hi Ganpat,
>>
>>  Are you able to see merers/samples related to compute.instance.* in
>> ceilometer meter-list or ceilometer sample-list.
>> My application which will read info from ceilometer publisher
>> (pipeline.yaml) and I am looking for meters realted to ceilometer.instance.*
>>
>> With Best Regards
>> Raghunath Dudyala
>> Tata Consultancy Services Limited
>> Mailto: raghunat...@tcs.com
>> Website: http://www.tcs.com
>> ____________
>> Experience certainty. IT Services
>> Business Solutions
>> Consulting
>> 
>>
>>
>> -Ganpat Agarwal <gans.develo...@gmail.com> wrote: -
>> To: "OpenStack Development Mailing List (not for usage questions)" <
>> openstack-dev@lists.openstack.org>
>> From: Ganpat Agarwal <gans.develo...@gmail.com>
>> Date: 10/25/2016 05:05PM
>> Subject: Re: [openstack-dev] [Ceilometer]: Instance creation and deletion
>> metrics in ceilometer !
>>
>>
>> Hi,
>>
>> I am able to get event notifications on kafka by applying these
>> configurations:
>>
>> nova.conf
>>
>> instance_usage_audit = True
>>
>> instance_usage_audit_period = hour
>>
>> notify_on_state_change = vm_and_task_state
>>
>> notification_driver = messagingv2
>>
>> Restart nova compute service
>>
>> ceilometer.conf
>>
>> [event]
>>
>> drop_unmatched_notifications = False
>>
>> definitions_cfg_file = /etc/ceilometer/event_definitions.yaml
>>
>>
>> event_pipeline.yaml
>>
>> ---
>>
>> sources:
>>
>> - name: event_source
>>
>>   events:
>>
>>  - compute.instance.*
>>
>>   sinks:
>>
>>   - event_sink
>>
>> sinks:
>>
>> - name: event_sink
>>
>>   transformers:
>>
>>   triggers:
>>
>>   publishers:
>>
>>   #- notifier://
>>
>>   #- file:///home/stack/test?max_bytes=1000_count=5
>>
>>   - kafka://kafka-broker:9092?topic=ceilometer
>>
>>
>> service 

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

[Ganpat Agarwal]

Hi Raghunath,

You can look at this file for details of meters related with
compute.instance.*

ceilometer/meter/data/meters.yaml

Additionally, you can look at this link for compute meters documentation

http://docs.openstack.org/admin-guide/telemetry-measurements.html


Also, have a look at "Meters definitions" section on this link

http://docs.openstack.org/admin-guide/telemetry-data-collection.html#meter-definitions

Regards,
Ganpat


On Tue, Oct 25, 2016 at 5:45 PM, Raghunath D <raghunat...@tcs.com> wrote:

> Hi Ganpat,
>
>  Are you able to see merers/samples related to compute.instance.* in
> ceilometer meter-list or ceilometer sample-list.
> My application which will read info from ceilometer publisher
> (pipeline.yaml) and I am looking for meters realted to ceilometer.instance.*
>
> With Best Regards
> Raghunath Dudyala
> Tata Consultancy Services Limited
> Mailto: raghunat...@tcs.com
> Website: http://www.tcs.com
> 
> Experience certainty. IT Services
> Business Solutions
> Consulting
> ____
>
>
> -Ganpat Agarwal <gans.develo...@gmail.com> wrote: -
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> From: Ganpat Agarwal <gans.develo...@gmail.com>
> Date: 10/25/2016 05:05PM
> Subject: Re: [openstack-dev] [Ceilometer]: Instance creation and deletion
> metrics in ceilometer !
>
>
> Hi,
>
> I am able to get event notifications on kafka by applying these
> configurations:
>
> nova.conf
>
> instance_usage_audit = True
>
> instance_usage_audit_period = hour
>
> notify_on_state_change = vm_and_task_state
>
> notification_driver = messagingv2
>
> Restart nova compute service
>
> ceilometer.conf
>
> [event]
>
> drop_unmatched_notifications = False
>
> definitions_cfg_file = /etc/ceilometer/event_definitions.yaml
>
>
> event_pipeline.yaml
>
> ---
>
> sources:
>
> - name: event_source
>
>   events:
>
>  - compute.instance.*
>
>   sinks:
>
>   - event_sink
>
> sinks:
>
> - name: event_sink
>
>   transformers:
>
>   triggers:
>
>   publishers:
>
>   #- notifier://
>
>   #- file:///home/stack/test?max_bytes=1000_count=5
>
>   - kafka://kafka-broker:9092?topic=ceilometer
>
>
> service ceilometer-api restart
>
> service ceilometer-agent-notification restart
>
>
> Wait for couple of minutes and you should be getting the events on your
> kafka consumer and in ceilometer notifications logs as well
>
> tail -f /var/log/ceilometer/ceilometer-agent-notification.log
>
>
> Let me know if it helps.
>
>
> Regards,
>
> Ganpat
>
>
>
> On Tue, Oct 25, 2016 at 3:02 PM, Raghunath D <raghunat...@tcs.com> wrote:
>
>> Hi ,
>>
>> Can some one please suggest how to instance notifications in ceilometer.
>>
>> With Best Regards
>> Raghunath Dudyala
>> Tata Consultancy Services Limited
>> Mailto: raghunat...@tcs.com
>> Website: http://www.tcs.com
>> 
>> Experience certainty. IT Services
>> Business Solutions
>> Consulting
>> 
>>
>>
>> -Raghunath D/HYD/TCS wrote: -
>> To: openstack-dev@lists.openstack.org
>> From: Raghunath D/HYD/TCS
>> Date: 10/18/2016 08:01PM
>> Subject: [openstack-dev] [Ceilometer]: Instance creation and deletion
>> metrics in ceilometer !
>>
>>
>> Hi ,
>>
>> How can instance created and deleted information/sample can be retrieved
>> from ceilometer.
>> What entries should be there in pipeline.yaml  to get instance deleted
>> information.
>>
>> I tried to have meters- "instance" in pipeline.yam but it always gives
>> active instance details,
>> and no details of deleted instances.
>>
>> With Best Regards
>> Raghunath Dudyala
>> Tata Consultancy Services Limited
>> Mailto: raghunat...@tcs.com
>> Website: http://www.tcs.com
>> 
>> Experience certainty. IT Services
>> Business Solutions
>> Consulting
>> 
>>
>> =-=-=
>> Notice: The information contained in this e-mail
>> message and/or attachments to it may contain
>> confidential or privileged information. If you are
>> not 

Re: [openstack-dev] [Ceilometer]: Instance creation and deletion metrics in ceilometer !

[Ganpat Agarwal]

Hi,

I am able to get event notifications on kafka by applying these
configurations:

nova.conf

instance_usage_audit = True

instance_usage_audit_period = hour

notify_on_state_change = vm_and_task_state

notification_driver = messagingv2

Restart nova compute service

ceilometer.conf

[event]

drop_unmatched_notifications = False

definitions_cfg_file = /etc/ceilometer/event_definitions.yaml


event_pipeline.yaml

---

sources:

- name: event_source

  events:

 - compute.instance.*

  sinks:

  - event_sink

sinks:

- name: event_sink

  transformers:

  triggers:

  publishers:

  #- notifier://

  #- file:///home/stack/test?max_bytes=1000_count=5

  - kafka://kafka-broker:9092?topic=ceilometer


service ceilometer-api restart

service ceilometer-agent-notification restart


Wait for couple of minutes and you should be getting the events on your
kafka consumer and in ceilometer notifications logs as well

tail -f /var/log/ceilometer/ceilometer-agent-notification.log


Let me know if it helps.


Regards,

Ganpat



On Tue, Oct 25, 2016 at 3:02 PM, Raghunath D  wrote:

> Hi ,
>
> Can some one please suggest how to instance notifications in ceilometer.
>
> With Best Regards
> Raghunath Dudyala
> Tata Consultancy Services Limited
> Mailto: raghunat...@tcs.com
> Website: http://www.tcs.com
> 
> Experience certainty. IT Services
> Business Solutions
> Consulting
> 
>
>
> -Raghunath D/HYD/TCS wrote: -
> To: openstack-dev@lists.openstack.org
> From: Raghunath D/HYD/TCS
> Date: 10/18/2016 08:01PM
> Subject: [openstack-dev] [Ceilometer]: Instance creation and deletion
> metrics in ceilometer !
>
>
> Hi ,
>
> How can instance created and deleted information/sample can be retrieved
> from ceilometer.
> What entries should be there in pipeline.yaml  to get instance deleted
> information.
>
> I tried to have meters- "instance" in pipeline.yam but it always gives
> active instance details,
> and no details of deleted instances.
>
> With Best Regards
> Raghunath Dudyala
> Tata Consultancy Services Limited
> Mailto: raghunat...@tcs.com
> Website: http://www.tcs.com
> 
> Experience certainty. IT Services
> Business Solutions
> Consulting
> 
>
> =-=-=
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [devstack]

[Ganpat Agarwal]

Hi All,

I have a openstack Havana setup running on Ubuntu 12.04 via Devstack.

I want to test the icehouse-1 milestone release (cinder and nova) on the
setup. I looked for the instructions in the docs but could not find.

Could anyone help me with the instructions or steps i should follow to
achieve this?

Thanks,
Gans
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [devstack]

[Ganpat Agarwal]

Thank you  Dean and Anne for your response.


On Wed, Dec 18, 2013 at 8:27 PM, Dean Troyer dtro...@gmail.com wrote:

 On Wed, Dec 18, 2013 at 8:23 AM, Anne Gentle 
 annegen...@justwriteclick.com wrote:

 Also, Dean correct me if I'm wrong, but I don't believe devstack does a
 precise milestone release. To guestimate it, you could figure out what


 This is correct, only stable/* releases.


 devstack looked like on 12/5 and get all the matching PROJECT_BRANCH=
 like this example localrc does:
 https://gist.github.com/everett-toews/4004430 I use this method to get
 stable/havana for example. Hat tip to Everett's blog at
 http://blog.phymata.com/2012/11/08/openstack-devstack-on-the-rackspace-open-cloud/
 .


 Actually, to do a stable/* release, check out that branch of DevStack, it
 has the correct stable branch settings in stackrc already.  But to do
 milestones, you would want DevStack somewhat close (for example, current
 DevStack master is still OK for the I-1 milestone) then set the XX_BRANCH
 variables manually.

 dt

 --

 Dean Troyer
 dtro...@gmail.com

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-dev][cinder][glance] Should glance be installed on cinder only nodes?

[Ganpat Agarwal]

Thanks Avishay.

I will try to setup a cinder-volume node and test this feature.

Regards,
Gans

On Tue, Dec 3, 2013 at 3:00 PM, Avishay Traeger avis...@il.ibm.com wrote:

 Gans,
 No, you don't need to install Glance on Cinder nodes.  Cinder will use the
 Glance client, which must be installed on the Cinder node (see
 python-glanceclient the requirements.txt file in Cinder's tree).

 Thanks,
 Avishay



 From:   gans developer gans.develo...@gmail.com
 To: openstack-dev@lists.openstack.org,
 Date:   12/03/2013 10:58 AM
 Subject:[openstack-dev] [OpenStack-dev][cinder][glance] Should
 glance be installed on cinder only nodes?



 Hi All,

 I was performing Copy Image to Volume operation on my controller node
 which has glance and cinder installed.

 If i wish to create a cinder only node for cinder-volume operations ,
 would i need to install glance also on this node for performing Copy
 Image to Volume operation ?

 Thanks,
 Gans.___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev