[Openstack] [openstack][icehouse][monitoring]-open source monitoring tools

[Chinasubbareddy M]

Hi ,

We would like to enable monitoring for 15 node openstack production setup, want 
suggestions up on following open source monitoring tools. Please suggest,


1.   Nagios and Cacti

2.   AppDynamics

3.   Zabbix and graphite

4.   Ganglia

It would be really helpful if you can suggest any other monitoring tools for 
openstack setup.

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [juno][DVR]

[Chinasubbareddy M]

Hi,

Can you please guide me for configuring the DVR in juno?
Referred the following link but was not able to do it as router create with 
distributed true failed to create the distributed router.

http://docs.openstack.org/networking-guide/content/ha-dvr.html

Regards,
Subbareddy.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [juno][DVR]

[Chinasubbareddy M]

Hi James,

Yes, I have the setup up and running with router and I manually installed the 
services.
I followed the link that I sent,  if I try to create the router with 
distributed option , it is getting failed .

Here is the output of the command:

root@junoos:~# neutron router-create --name another_router --distributed True
Invalid input for name. Reason: 'True' is not a valid string. (HTTP 400) 
(Request-ID: req-96e0bcab-a9ec-43b8-af68-de55c3ed4a43)

My other doubt in the link , asking to make changes in ml2_conf.ini and 
ovs_neutron_plugin.ini
But I am using only ml2 plugin , please suggest.


Regards,
Subbareddy.


From: James Denton [mailto:james.den...@rackspace.com]
Sent: Tuesday, December 30, 2014 9:42 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: RE: [Openstack] [juno][DVR]

Subbareddy,

I have been working on this over the last day or so, and have been using the 
link you sent as reference. It is lacking in a few details, however, I got it 
to work.

A couple of questions:

1. Did you have a working legacy router configuration prior to messing with DVR?
2. Did you have a working GRE/VXLAN tenant network that used the legacy router?

I recommend setting up a legacy router first, testing it, and then making the 
few modifications to get DVR working once you have a concrete network setup. 
I'm happy to provide you with those steps once I polish them up a little bit.

James

From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Saturday, December 27, 2014 2:52 PM
To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: [Openstack] [juno][DVR]
Hi,

Can you please guide me for configuring the DVR in juno?
Referred the following link but was not able to do it as router create with 
distributed true failed to create the distributed router.

http://docs.openstack.org/networking-guide/content/ha-dvr.html

Regards,
Subbareddy.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [juno][DVR]

[Chinasubbareddy M]

Hi James,

If I try with out --name, this is the output,

root@junoos:~# neutron router-create another_router --distributed True
Not Implemented (HTTP 501) (Request-ID: 
req-ed06ba44-48db-46ff-810d-1b323e03d651)
root@junoos:~#

From: James Denton [mailto:james.den...@rackspace.com]
Sent: Thursday, January 01, 2015 9:56 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: RE: [Openstack] [juno][DVR]

Hi Subbareddy,

Have you tried without --name?

[root@controller ~]# neutron router-create another_router --distributed True
Created a new router:
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| distributed   | True |
| external_gateway_info |  |
| ha| False|
| id| 58f8b03d-f230-4dcb-be7b-71c73a167e41 |
| name  | another_router   |
| routes|  |
| status| ACTIVE   |
| tenant_id | 00b1617b007d41b7aa777e0c97afdccc |
+---+--+

James

From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Wednesday, December 31, 2014 5:06 AM
To: James Denton; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]
Hi James,

Yes, I have the setup up and running with router and I manually installed the 
services.
I followed the link that I sent,  if I try to create the router with 
distributed option , it is getting failed .

Here is the output of the command:

root@junoos:~# neutron router-create --name another_router --distributed True
Invalid input for name. Reason: 'True' is not a valid string. (HTTP 400) 
(Request-ID: req-96e0bcab-a9ec-43b8-af68-de55c3ed4a43)

My other doubt in the link , asking to make changes in ml2_conf.ini and 
ovs_neutron_plugin.ini
But I am using only ml2 plugin , please suggest.


Regards,
Subbareddy.


From: James Denton [mailto:james.den...@rackspace.com]
Sent: Tuesday, December 30, 2014 9:42 PM
To: Chinasubbareddy M; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]

Subbareddy,

I have been working on this over the last day or so, and have been using the 
link you sent as reference. It is lacking in a few details, however, I got it 
to work.

A couple of questions:

1. Did you have a working legacy router configuration prior to messing with DVR?
2. Did you have a working GRE/VXLAN tenant network that used the legacy router?

I recommend setting up a legacy router first, testing it, and then making the 
few modifications to get DVR working once you have a concrete network setup. 
I'm happy to provide you with those steps once I polish them up a little bit.

James
________
From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Saturday, December 27, 2014 2:52 PM
To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: [Openstack] [juno][DVR]
Hi,

Can you please guide me for configuring the DVR in juno?
Referred the following link but was not able to do it as router create with 
distributed true failed to create the distributed router.

http://docs.openstack.org/networking-guide/content/ha-dvr.html

Regards,
Subbareddy.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it

Re: [Openstack] [juno][DVR]

[Chinasubbareddy M]

Thank you so much James, finally it got worked and I am able to create the 
router(DVR).

From: James Denton [mailto:james.den...@rackspace.com]
Sent: Friday, January 02, 2015 9:54 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: RE: [Openstack] [juno][DVR]

Hi Subbareddy,

Can you run that command again and then take a look at 
/var/log/neutron/server.log? It should give some indication as to what went 
wrong.

If you'd like, I wouldn't mind seeing your l3_agent.ini, neutron.conf, and 
ml2_conf.ini from the controller/compute nodes if you want to post them 
somewhere.

James
____
From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Thursday, January 01, 2015 6:26 PM
To: James Denton; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]
Hi James,

If I try with out --name, this is the output,

root@junoos:~# neutron router-create another_router --distributed True
Not Implemented (HTTP 501) (Request-ID: 
req-ed06ba44-48db-46ff-810d-1b323e03d651)
root@junoos:~#

From: James Denton [mailto:james.den...@rackspace.com]
Sent: Thursday, January 01, 2015 9:56 PM
To: Chinasubbareddy M; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]

Hi Subbareddy,

Have you tried without --name?

[root@controller ~]# neutron router-create another_router --distributed True
Created a new router:
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| distributed   | True |
| external_gateway_info |  |
| ha| False|
| id| 58f8b03d-f230-4dcb-be7b-71c73a167e41 |
| name  | another_router   |
| routes|  |
| status| ACTIVE   |
| tenant_id | 00b1617b007d41b7aa777e0c97afdccc |
+---+--+

James
____
From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Wednesday, December 31, 2014 5:06 AM
To: James Denton; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]
Hi James,

Yes, I have the setup up and running with router and I manually installed the 
services.
I followed the link that I sent,  if I try to create the router with 
distributed option , it is getting failed .

Here is the output of the command:

root@junoos:~# neutron router-create --name another_router --distributed True
Invalid input for name. Reason: 'True' is not a valid string. (HTTP 400) 
(Request-ID: req-96e0bcab-a9ec-43b8-af68-de55c3ed4a43)

My other doubt in the link , asking to make changes in ml2_conf.ini and 
ovs_neutron_plugin.ini
But I am using only ml2 plugin , please suggest.


Regards,
Subbareddy.


From: James Denton [mailto:james.den...@rackspace.com]
Sent: Tuesday, December 30, 2014 9:42 PM
To: Chinasubbareddy M; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: RE: [Openstack] [juno][DVR]

Subbareddy,

I have been working on this over the last day or so, and have been using the 
link you sent as reference. It is lacking in a few details, however, I got it 
to work.

A couple of questions:

1. Did you have a working legacy router configuration prior to messing with DVR?
2. Did you have a working GRE/VXLAN tenant network that used the legacy router?

I recommend setting up a legacy router first, testing it, and then making the 
few modifications to get DVR working once you have a concrete network setup. 
I'm happy to provide you with those steps once I polish them up a little bit.

James
____
From: Chinasubbareddy M [chinasubbaredd...@persistent.com]
Sent: Saturday, December 27, 2014 2:52 PM
To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: [Openstack] [juno][DVR]
Hi,

Can you please guide me for configuring the DVR in juno?
Referred the following link but was not able to do it as router create with 
distributed true failed to create the distributed router.

http://docs.openstack.org/networking-guide/content/ha-dvr.html

Regards,
Subbareddy.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communica

[Openstack] [Icehouse][neutron][manto-to-one NAT]

[Chinasubbareddy M]

HI all,

I would like to understand many to one NAT feature  by neutron , so I have 
created a gateway for router with "enable_snat" on disable mode, now I am 
confused how to use many to one NAT, can you please guide me ?

root@vpnaas1:~# neutron router-show 1dc4a054-1a93-4962-abaa-01f118a3
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| external_gateway_info | {"network_id": 
"bc9172f9-25e7-454b-a387-d81ee79be74d", "enable_snat": false} |
| id| 1dc4a054-1a93-4962-abaa-01f118a3  
   |
| name  | router1   
   |
| routes|   
   |
| status| ACTIVE
   |
| tenant_id | 4123b6cff1124795959f4dc73e82531a  
   |
+---+--+
root@vpnaas1:~#


Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Icehouse][neutron][manto-to-one NAT]

[Chinasubbareddy M]

Thank you James.

I am looking for an option where I will be having only one public IP and then 
users outside to cloud will use that IP to connect to the VMs inside the cloud.

For example vm whose local ip is 1.1.1.2 and the public ip for the setup is 
192.168.10.11.
If a user outside to cloud connect to pot 422 of 192.168.10.11 then it should 
redirect to 22 port of 1.1.1.2

I would like to know neutron has this feature or not .

Regards,
Subbareddy.



From: James Denton [mailto:james.den...@rackspace.com]
Sent: Wednesday, January 21, 2015 9:27 PM
To: Chinasubbareddy M
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] [Icehouse][neutron][manto-to-one NAT]

Hi Subbareddy,

SNAT, or source NAT, is the ‘many-to-one’ NAT mode you are referring to. 
Instances that do not have a floating IP will be NAT’d to the IP address of the 
qg interface of the router. This is akin to a PAT on other firewalls.

A floating IP is akin to a static 1-to-1 NAT, and takes precedence over the 
default SNAT behavior.

By setting enable_snat to false, your traffic is being forwarded out of the 
router as the fixed IP of the instance.

James

On Jan 21, 2015, at 8:15 AM, Chinasubbareddy M 
mailto:chinasubbaredd...@persistent.com>> 
wrote:

HI all,

I would like to understand many to one NAT feature  by neutron , so I have 
created a gateway for router with "enable_snat” on disable mode, now I am 
confused how to use many to one NAT, can you please guide me ?

root@vpnaas1:~# neutron router-show 1dc4a054-1a93-4962-abaa-01f118a3
+---+--+
| Field | Value 
   |
+---+--+
| admin_state_up| True  
   |
| external_gateway_info | {"network_id": 
"bc9172f9-25e7-454b-a387-d81ee79be74d", "enable_snat": false} |
| id| 1dc4a054-1a93-4962-abaa-01f118a3  
   |
| name  | router1   
   |
| routes|   
   |
| status| ACTIVE
   |
| tenant_id | 4123b6cff1124795959f4dc73e82531a  
   |
+---+--+
root@vpnaas1:~#


Regards,
Subbareddy,
Persistent systems ltd.
DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack-dev] Openstack Network Node High Availability [openstack]

[Chinasubbareddy M]

Hi,

As per my knowledge DVR is to avoid neutron node as an single point of failure 
and distribute l3 operations across compute nodes.

HA for L3 agents is working from Juno but it will be on active/passive mode, 
only one l3 will be on active at a time .

Subbareddy,
Persistent systems ltd.

From: Vikash Kumar [mailto:vikash.ku...@oneconvergence.com]
Sent: Thursday, January 29, 2015 11:32 AM
To: Openstack Milis; openstack-dev
Subject: Re: [Openstack] [openstack-dev] Openstack Network Node High 
Availability [openstack]

Is DVR a possible way to some extent(loosely)  to address HA of l3 agents ?

On Thu, Jan 29, 2015 at 11:08 AM, Vikash Kumar 
mailto:vikash.ku...@oneconvergence.com>> wrote:
Hi,
Is there any work going on High Availability of Network Node or is there 
any existing work? I see doc. on running multiple dhcp agent on multiple node 
but do not got on l3 agent. Is there any doc having details of running multiple 
dhcp agents on multiple hosts?

--
Regards,
Vikash

__
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



--
Regards,
Vikash

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [autoscaling][icehouse]

[Chinasubbareddy M]

Hi ,

Could you please share working auto scaling script which helps understanding 
the auto scaling in openstack cloud ?

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][ceilometer][webhook]

[Chinasubbareddy M]

Hello,

I have a running instance of ceilometer in my system, I want to create an alarm 
through ceilometer without using heat template. There is a command line API 
called ceilometer alarm-create.

Now I want the alarm in such a way that it will trigger an instance creation 
after a value is greater than the threshold. I know that [--alarm-action 
] serves the purpose. But what should i put in the Webhook url??

How do i generate a webhook url which will tell ceilometer to create an 
instance?

Can some body help me with regards to this web hook url?

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [autoscaling][icehouse]

[Chinasubbareddy M]

Hi,

Thanks for the blog , but I am  getting the below error while I am launching 
the stack as per the instructions.

StackValidationFailed: Unknown resource Type : OS::Nova::Server::Cirros

One more problem is creating the volume from a vm , can't we  boot the vm 
without cinder resource?

Regards,
Subbareddy.

-Original Message-
From: Christian Berendt [mailto:christ...@berendt.io] 
Sent: Monday, March 02, 2015 2:20 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [autoscaling][icehouse]

On 03/02/2015 06:31 AM, Chinasubbareddy M wrote:
> Could you please share working auto scaling script which helps 
> understanding the auto scaling in openstack cloud ?

https://blog.berendt.io/simple-auto-scaling-environment-with-heat/

HTH, Christian.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [autoscaling][icehouse]

[Chinasubbareddy M]

Hi,
I am using the same command to crate the stack and here is the version of heat:

root@build-server:~# heat --version
0.2.8

From: Steve Baker [mailto:sba...@redhat.com]
Sent: Wednesday, March 04, 2015 4:00 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [autoscaling][icehouse]

On 04/03/15 00:00, Chinasubbareddy M wrote:

Hi,



Thanks for the blog , but I am  getting the below error while I am launching 
the stack as per the instructions.



StackValidationFailed: Unknown resource Type : OS::Nova::Server::Cirros


Assuming you ran the following, what version of python-heatclient do you have 
installed?
  heat stack-create simple -f simple.yaml -e environment.yaml


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][autoscaling][icehouse][OS::Heat:: AutoScalingGroup]

[Chinasubbareddy M]

Hi,

I am testing openstack auto scaling function, but  the stack is getting failed 
with below error,

:Multiple possible networks found, use a Network ID to be more specific

could anybody tell me how to solve it? ,
This is happening in case of using  OS::Heat:: AutoScalingGroup  resource,  is 
there any way to mention network id in this resource?

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.



autoscaling.yaml
Description: autoscaling.yaml
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][autoscaling][icehouse][OS::Heat:: AutoScalingGroup]

[Chinasubbareddy M]

Thank you Deepthi, its working now .

-Original Message-
From: Deepthi Dharwar [mailto:deep...@linux.vnet.ibm.com] 
Sent: Wednesday, March 04, 2015 4:18 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][autoscaling][icehouse][OS::Heat:: 
AutoScalingGroup]

On 03/04/2015 02:36 PM, Chinasubbareddy M wrote:
> Hi,
> 
>  
> 
> I am testing openstack auto scaling function, but  the stack is 
> getting failed with below error,
> 
>  
> 
> :Multiple possible networks found, use a Network ID to be more 
> specific
> 
>  
> 
> could anybody tell me how to solve it? ,
> 
> This is happening in case of using  OS::Heat::AutoScalingGroup  
> resource,  is there any way to mention network id in this resource?

In your load balancer yaml, i.e lb_server.yaml Add the following:

Under 'parameters' add network id

parameters:
private_net_id:
type: string
default: 


And under resources:

member:
type: OS::Neutron::PoolMember
properties:
  pool_id: {get_param: pool_id}
  address: {get_attr: [server, first_address]}
  protocol_port: 80
  server_port:
type: OS::Neutron::Port
properties:
  network_id: { get_param: private_net_id } => add the network id.
  fixed_ips:
- subnet_id: { get_param: subnet_id }

This should help you specify the network in which you want to plug in your VMs.

Regards,
Deepthi



>  
> 
> Regards,
> 
> Subbareddy,
> 
> Persistent systems ltd.
> 
> DISCLAIMER == This e-mail may contain privileged and 
> confidential information which is the property of Persistent Systems 
> Ltd. It is intended only for the use of the individual or entity to 
> which it is addressed. If you are not the intended recipient, you are 
> not authorized to read, retain, copy, print, distribute or use this 
> message. If you have received this communication in error, please 
> notify the sender and delete all copies of this message. Persistent 
> Systems Ltd. does not accept any liability for virus infected mails.
> 
> 
> 
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [autoscaling][icehouse][OS::Heat::AutoScalingGroup]

[Chinasubbareddy M]

03-05T14:15:57.808676 | state: insufficient data  
  |
| state transition | 2015-03-05T14:23:57.876373 | state: alarm  
  |
| state transition | 2015-03-05T14:25:57.856860 | state: insufficient data  
  |
| state transition | 2015-03-05T14:33:57.999285 | state: alarm  
  |
| state transition | 2015-03-05T14:35:57.928619 | state: insufficient data  
  |
| state transition | 2015-03-05T14:43:58.000641 | state: alarm  
  |
| state transition | 2015-03-05T14:45:57.994070 | state: insufficient data  
  |
| rule change  | 2015-03-05T14:46:28.934119 | repeat_actions: True  
  |
| state transition | 2015-03-05T14:53:58.274025 | state: alarm  
  |
| state transition | 2015-03-05T14:55:58.039142 | state: insufficient data  
  |
+--++-+

-Original Message-
From: Chinasubbareddy M
Sent: Thursday, March 05, 2015 5:38 PM
To: 'Deepthi Dharwar'; openstack@lists.openstack.org
Subject: RE: [Openstack] [openstack][autoscaling][icehouse][OS::Heat:: 
AutoScalingGroup]

Thank you Deepthi, its working now .

-Original Message-
From: Deepthi Dharwar [mailto:deep...@linux.vnet.ibm.com]
Sent: Wednesday, March 04, 2015 4:18 PM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][autoscaling][icehouse][OS::Heat:: 
AutoScalingGroup]

On 03/04/2015 02:36 PM, Chinasubbareddy M wrote:
> Hi,
>
>
>
> I am testing openstack auto scaling function, but  the stack is
> getting failed with below error,
>
>
>
> :Multiple possible networks found, use a Network ID to be more
> specific
>
>
>
> could anybody tell me how to solve it? ,
>
> This is happening in case of using  OS::Heat::AutoScalingGroup
> resource,  is there any way to mention network id in this resource?

In your load balancer yaml, i.e lb_server.yaml Add the following:

Under 'parameters' add network id

parameters:
private_net_id:
type: string
default: 


And under resources:

member:
type: OS::Neutron::PoolMember
properties:
  pool_id: {get_param: pool_id}
  address: {get_attr: [server, first_address]}
  protocol_port: 80
  server_port:
type: OS::Neutron::Port
properties:
  network_id: { get_param: private_net_id } => add the network id.
  fixed_ips:
- subnet_id: { get_param: subnet_id }

This should help you specify the network in which you want to plug in your VMs.

Regards,
Deepthi



>
>
> Regards,
>
> Subbareddy,
>
> Persistent systems ltd.
>
> DISCLAIMER == This e-mail may contain privileged and
> confidential information which is the property of Persistent Systems
> Ltd. It is intended only for the use of the individual or entity to
> which it is addressed. If you are not the intended recipient, you are
> not authorized to read, retain, copy, print, distribute or use this
> message. If you have received this communication in error, please
> notify the sender and delete all copies of this message. Persistent
> Systems Ltd. does not accept any liability for virus infected mails.
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.



autoscaling.yaml
Description: autoscaling.yaml
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [autoscaling][icehouse]

[Chinasubbareddy M]

Hi,

While I am troubleshooting this problem ,I changed the webhook to my own 
webhook which is of shell script  and it is getting triggered by ceilometer 
alarm.
So the problem is with heat based webhook in the alarm . 

could you please help me out here?

Regards,
Subbareddy.



-Original Message-
From: Chinasubbareddy M 
Sent: Thursday, March 05, 2015 8:27 PM
To: 'Deepthi Dharwar'; 'openstack@lists.openstack.org'
Cc: David Peraza
Subject: RE: [Openstack][autoscaling][icehouse][OS::Heat::AutoScalingGroup]

Hello all,

I can see the alarm in alarm-history. However, no actions are triggered.
Could you please help me out here ?

Here is the alarm-show :

root@build-server:~# ceilometer alarm-show --alarm_id 
ec8d3a5f-f890-465e-b796-dba2cf2c12fe
+---+--+
| Property  | Value 
   |
+---+--+
| alarm_actions | 
[u'http://10.44.191.200:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e9 |
|   | 
3810a7c4be2881bd7ede428526a%3Astacks%2FasworkingFinal%2F31f62d11-401e-   |
|   | 
435b-a2a7-1e5318ce8159%2Fresources%2Fweb_server_scaleup_policy?Timestamp |
|   | 
=2015-03-04T13%3A13%3A31Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=8216 |
|   | 
7ae13f3240e5aa6f1d6a5c4f39d3&SignatureVersion=2&Signature=fOH%2Fny5BpzbL |
|   | qwWce1qHyqAjBn9YXR0F%2FPlzeeJCdYc%3D']
   |
| alarm_id  | ec8d3a5f-f890-465e-b796-dba2cf2c12fe  
   |
| comparison_operator   | gt
   |
| description   | Scale-up if the average CPU > 50% for 1 minute
   |
| enabled   | True  
   |
| evaluation_periods| 1 
   |
| exclude_outliers  | False 
   |
| insufficient_data_actions | []
   |
| meter_name| cpu_util  
   |
| name  | asworkingFinal-cpu_alarm_high-swtpxt4coqme
   |
| ok_actions| []
   |
| period| 60
   |
| project_id| ec3e93810a7c4be2881bd7ede428526a  
   |
| query | metadata.user_metadata.stack == 
31f62d11-401e-435b-a2a7-1e5318ce8159 |
| repeat_actions| True  
   |
| state | alarm 
   |
| statistic | avg   
   |
| threshold | 50.0  
   |
| type  | threshold 
   |
| user_id   | cac9bb03d57f41359df9b12c4b6d2318  
   |
+---+--+

Here is the output of alarm history:

| state transition | 2015-03-05T13:05:57.360308 | state: insufficient data  
  |
| state transition | 2015-03-05T13:13:57.514774 | state: alarm  
  |
| state transition | 2015-03-05T13:14:57.438538 | state: insufficient data  
  |
| state transition | 2015-03-05T13:23:57.578754 | state: alarm  
  |
| state transition | 2015-03-05T13:24:57.497549 | state: insufficient data  
  |
| state transition | 2015-03-05T13:33:57.583486 | state: alarm  
  |
| state transition | 2015-03-05T13:34:57.559243 | state: insufficient data  
  |
| state transition | 2015-03-05T13:43:57.693379 | state: alarm  
  |
| state transition | 2015-03-05T13:44:57.605715 | state: insufficient data  
  |
| state trans

[Openstack] [openstack][[autoscaling][icehouse]

[Chinasubbareddy M]

Hi ,

as I wanted to check out the autoscaling features of heat in combination with 
ceilometer, I tried to adapt one of the example HOT's. Meanwhile, the HOT is 
starting successfully, but whatever I do to stress my VM in the 
web_server_group, no scaling reaction is observable.

Executing the webhook manually, there's an error response, which google hardly 
knows, so I try my best here - maybe you can help me to solve this problem.
Additionally I'm wondering, why AWS is mentioned in the error - actually I 
don't want to use it. Are webhooks only possible via AWS?

root@build-server:~# ceilometer alarm-show -a 
8ff22ef8-268a-4803-8350-7c8f1f02aa39

+---+--+

| Property  | Value 
   |

+---+--+

| alarm_actions | 
[u'http://127.0.0.1:8004/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810 |

|   | 
a7c4be2881bd7ede428526a%3Astacks%2Fsrujana2%2Fcb249f69-baa3-40b3-90a7-34 |

|   | 
7fe5dbe843%2Fresources%2Fweb_server_scaleup_policy?Timestamp=2015-03-10T |

|   | 
06%3A19%3A05Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=2b8e2175a0e747bb |

|   | 
b8a9c6f33424758c&SignatureVersion=2&Signature=JKEnz57aaAaSNOWbmOD%2FYrUu |

|   | 14ZQy5HatdK9ffA1VwU%3D']  
   |

| alarm_id  | 8ff22ef8-268a-4803-8350-7c8f1f02aa39  
   |

| comparison_operator   | gt
   |

| description   | Scale-up if the average CPU > 50% for 1 minute
   |

| enabled   | True  
   |

| evaluation_periods| 1 
   |

| exclude_outliers  | False 
   |

| insufficient_data_actions | []
   |

| meter_name| cpu_util  
   |

| name  | srujana2-cpu_alarm_high-vtqkmn3ts4z3  
   |

| ok_actions| []
   |

| period| 60
   |

| project_id| ec3e93810a7c4be2881bd7ede428526a  
   |

| query | metadata.user_metadata.stack == 
cb249f69-baa3-40b3-90a7-347fe5dbe843 |

| repeat_actions| False 
   |

| state | insufficient data 
   |

| statistic | avg   
   |

| threshold | 50.0  
   |

| type  | threshold 
   |

| user_id   | cac9bb03d57f41359df9b12c4b6d2318  
   |

+---+--+


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat][Ceilometer][Autoscaling]

[Chinasubbareddy M]

Hi,

We used to have Ip address only , while troubleshooting we made that to 
localhost.
If you see the url , there is AWS access key and if we execute the url manually 
, its getting failed to contact keystone and get token.

If we get the token manually and request it again ,it's getting failed with 
unknown heat resource.

It would be easy if you can share any working template which is generating 
proper webhook.


Regards,
Subbareddy,
Persistent systems.



-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] 
Sent: Wednesday, March 11, 2015 3:00 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]

Checked your alarm_url string again, it seems that your heat.conf file contains 
this line:

heat_waitcondition_server_url=http://:8000/waitcondition

You have to change  to the IP of the heat-cfn-api service host.

Regards,
 Qiming

On Tue, Mar 10, 2015 at 10:47:10AM +, Srujana C P wrote:
> Hi,
> 
> I would like to explore on auto scaling functionality of heat. So I 
> have started with sample word press template available. It could 
> create a stack(alarms, instance, etc., ). However, alarm is not 
> getting triggered whenever I put stress on it. The alarm_action 
> assigned to the alarm created from the template is Alarm_action : 
> http://:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2 /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c4b
> e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2cf3
> 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2> 
> 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=3013
> 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRPOT
> 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D
> 
> This alarm_url is not doing required scaling action. So, in order to confirm 
> whether the alarm has been hit, I just modified alarm action with some script 
> url. I could see the script got executed.
> 
> Can someone please help me on below queries
> 
> 1.   How this alarm_url got generated?
> 
> 2.   Why this has AWSAccesskeyId details? To which access key it is 
> referring to?
> 
> 3.   What changes need to be done to execute the above mentioned alarm 
> url?
> 
> 4.   How to configure heat to authenticate with Openstack?
> 
> Any help on this would be very thankful.
> 
> Thanks,
> Srujana
> 
> 
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is the 
> property of Persistent Systems Ltd. It is intended only for the use of the 
> individual or entity to which it is addressed. If you are not the intended 
> recipient, you are not authorized to read, retain, copy, print, distribute or 
> use this message. If you have received this communication in error, please 
> notify the sender and delete all copies of this message. Persistent Systems 
> Ltd. does not accept any liability for virus infected mails.
> 



> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][[autoscaling][icehouse]

[Chinasubbareddy M]

Hi,

Alarm state is going to alarm and its hitting the webhook , to confirm that I 
kept my own webhook, its getting executed whenever alarm triggered.

Problem is with webhook generated by heat .

alarm_actions | 
[u'http://10.44.191.200:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810 |
|   | 
a7c4be2881bd7ede428526a%3Astacks%2Fsrujana2%2Fcb249f69-baa3-40b3-90a7-34 |
|   | 
7fe5dbe843%2Fresources%2Fweb_server_scaleup_policy?Timestamp=2015-03-10T |
|   | 
06%3A19%3A05Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=2b8e2175a0e747bb |
|   | 
b8a9c6f33424758c&SignatureVersion=2&Signature=JKEnz57aaAaSNOWbmOD%2FYrUu |
|   | 14ZQy5HatdK9ffA1VwU%3D']  
   |
| alarm_id  | 8ff22ef8-268a-4803-8350-7c8f1f02aa39


Why AWS key is there in the url ?

Regards,
Subbareddy.



-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] 
Sent: Wednesday, March 11, 2015 3:05 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][[autoscaling][icehouse]

On Tue, Mar 10, 2015 at 07:12:54AM +, Chinasubbareddy M wrote:
> Hi ,
> 
> as I wanted to check out the autoscaling features of heat in combination with 
> ceilometer, I tried to adapt one of the example HOT's. Meanwhile, the HOT is 
> starting successfully, but whatever I do to stress my VM in the 
> web_server_group, no scaling reaction is observable.
> 
> Executing the webhook manually, there's an error response, which google 
> hardly knows, so I try my best here - maybe you can help me to solve this 
> problem.
> Additionally I'm wondering, why AWS is mentioned in the error - actually I 
> don't want to use it. Are webhooks only possible via AWS?
> 
> root@build-server:~# ceilometer alarm-show -a 
> 8ff22ef8-268a-4803-8350-7c8f1f02aa39
> 
> +---+--+
> 
> | Property  | Value   
>  |
> 
> +---+--+
> 
> | alarm_actions | 
> [u'http://127.0.0.1:8004/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810 |
> 
> |   | 
> | a7c4be2881bd7ede428526a%3Astacks%2Fsrujana2%2Fcb249f69-baa3-40b3-90a
> | 7-34 |
> 
> |   | 
> | 7fe5dbe843%2Fresources%2Fweb_server_scaleup_policy?Timestamp=2015-03
> | -10T |
> 
> |   | 
> | 06%3A19%3A05Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=2b8e2175a0e7
> | 47bb |
> 
> |   | 
> | b8a9c6f33424758c&SignatureVersion=2&Signature=JKEnz57aaAaSNOWbmOD%2F
> | YrUu |
> 
> |   | 14ZQy5HatdK9ffA1VwU%3D']
>  |
> 
> | alarm_id  | 8ff22ef8-268a-4803-8350-7c8f1f02aa39
>  |
> 
> | comparison_operator   | gt  
>  |
> 
> | description   | Scale-up if the average CPU > 50% for 1 minute  
>  |
> 
> | enabled   | True
>  |
> 
> | evaluation_periods| 1   
>  |
> 
> | exclude_outliers  | False   
>  |
> 
> | insufficient_data_actions | []  
>  |
> 
> | meter_name| cpu_util
>  |
> 
> | name  | srujana2-cpu_alarm_high-vtqkmn3ts4z3
>  |
> 
> | ok_actions| []  
>  |
> 
> | period| 60  
>  |
> 
> | project_id| ec3e93810a7c4be2881bd7ede428526a
>  |
> 
> | query | metadata.user_metadata.stack == 
> cb249f69-baa3-40b3-90a7-347fe5dbe843 |
> 
> | repeat_actions| False   
>  |
> 
> | state | insufficient data   
>   

Re: [Openstack] [Heat][Ceilometer][Autoscaling]

[Chinasubbareddy M]

Hi,

Thank you Qiming  , finally it worked and problem was with auth uri  in 
ec2token section , it has " /ec2token"  ,  after removing it  auto scaling 
started working .

This is the final working  parameter:

[ec2authtoken]
auth_uri=http://1.2.3.4:5000/v2.0

-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] 
Sent: Wednesday, March 11, 2015 2:52 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]


> > http://:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a
> > 7c 
> > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > 2c 
> > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2 > :/ 
> > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > 4b
> > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > 13 
> > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > OT 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D

The alarm_url above shows that the  part is hardcoded in your heat.conf 
file.

Seems that your authentication to Keystone using ec2token has failed?
You may check if you have the following settings in your heat.conf file:

[ec2authtoken]
auth_uri=http://1.2.3.4:5000/v2.0

That is one reason that could lead to the problem you have met. Another thing 
to check is whether you have ec2 service configured in Keystone:

$ keystone service-list | grep ec2

It was for compatibility's reason that Heat uses EC2 token authentication for 
the alarm url, as I have mentioned in previous replies.

Regards,
  Qiming

On Tue, Mar 10, 2015 at 01:44:17PM +, Chinasubbareddy M wrote:
> Hi,
> 
> We used to have Ip address only , while troubleshooting we made that to 
> localhost.
> If you see the url , there is AWS access key and if we execute the url 
> manually , its getting failed to contact keystone and get token.
> 
> If we get the token manually and request it again ,it's getting failed with 
> unknown heat resource.
> 
> It would be easy if you can share any working template which is generating 
> proper webhook.
> 
> 
> Regards,
> Subbareddy,
> Persistent systems.
> 
> 
> 
> -Original Message-
> From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com]
> Sent: Wednesday, March 11, 2015 3:00 AM
> To: openstack@lists.openstack.org
> Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]
> 
> Checked your alarm_url string again, it seems that your heat.conf file 
> contains this line:
> 
> heat_waitcondition_server_url=http://:8000/waitcondition
> 
> You have to change  to the IP of the heat-cfn-api service host.
> 
> Regards,
>  Qiming
> 
> On Tue, Mar 10, 2015 at 10:47:10AM +, Srujana C P wrote:
> > Hi,
> >
> > I would like to explore on auto scaling functionality of heat. So I 
> > have started with sample word press template available. It could 
> > create a stack(alarms, instance, etc., ). However, alarm is not 
> > getting triggered whenever I put stress on it. The alarm_action 
> > assigned to the alarm created from the template is Alarm_action :
> > http://:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a
> > 7c 
> > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > 2c 
> > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2 > :/ 
> > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > 4b
> > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > 13 
> > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > OT 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D
> >
> > This alarm_url is not doing required scaling action. So, in order to 
> > confirm whether the alarm has been hit, I just modified alarm action with 
> > some script url. I could see the script got executed.
> >
> > Can someone please help me on below queries
> >
> > 1.   How this alarm_url got generated?
> >
> > 2.   Why this has AWSAccesskeyId details? To which access key it is 
> > referring to?
> >
> > 3.   What changes need to be done to execute the above mentioned alarm 
> > url?
> >
> > 4.   How to configure heat to authenticate with Openstack?
> >
> > Any help on this would be very thankful.

[Openstack] [openstack][ceilometer][icehouse]

[Chinasubbareddy M]

Hello all,

need to write a code in python to Implement a new custom meter data in 
ceilometer, could you please help me out with your suggestion ?

my intention is to collect the application sample data through that new meter 
and implement auto scaling .

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Virtual instance access to openstack controller

[Chinasubbareddy M]

Configure floatins ips  or provider networks are the solutions.

https://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks/

From: Kamsali, RaghavendraChari (Artesyn) 
[mailto:raghavendrachari.kams...@artesyn.com]
Sent: Friday, March 13, 2015 11:27 AM
To: openstack@lists.openstack.org
Subject: [Openstack] Virtual instance access to openstack controller

Hi,

I have one query regarding Openstack Neutron Networking ,
How to make virtual instance access to OpenStack Controller via management 
place and virtual instance is configured with Data Interface(virtual network).


Thanks and Regards,
Raghavendrachari kamsali | Software Engineer II  | Embedded Computing
Artesyn Embedded Technologies | 5th Floor, Capella Block, The V, Madhapur| 
Hyderabad, AP 500081 India
T +91-40-66747059 | M +919705762153


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [Heat][Ceilometer][Autoscaling]

[Chinasubbareddy M]

Hello Qiming,

When I put stress on the server, it is adding one more node to the auto scaling 
group. So I would like to know for the next scaling action to perform, is 
ceilometer alarm is raised based on the load on all existing machines in the 
auto scaling group or individual servers in the group.

As Ceilometer is not considering stack as its resource, How it would calculate 
the statistics for the entire stack?

Regards,
Subbareddy,
Persistent systems ltd.

-Original Message-
From: Chinasubbareddy M 
Sent: Wednesday, March 11, 2015 6:55 PM
To: 'Qiming Teng'; openstack@lists.openstack.org
Cc: David Peraza
Subject: RE: [Openstack] [Heat][Ceilometer][Autoscaling]

Hi,

Thank you Qiming  , finally it worked and problem was with auth uri  in 
ec2token section , it has " /ec2token"  ,  after removing it  auto scaling 
started working .

This is the final working  parameter:

[ec2authtoken]
auth_uri=http://1.2.3.4:5000/v2.0

-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] 
Sent: Wednesday, March 11, 2015 2:52 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]


> > http://:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a
> > 7c 
> > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > 2c 
> > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2 > :/ 
> > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > 4b
> > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > 13 
> > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > OT 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D

The alarm_url above shows that the  part is hardcoded in your heat.conf 
file.

Seems that your authentication to Keystone using ec2token has failed?
You may check if you have the following settings in your heat.conf file:

[ec2authtoken]
auth_uri=http://1.2.3.4:5000/v2.0

That is one reason that could lead to the problem you have met. Another thing 
to check is whether you have ec2 service configured in Keystone:

$ keystone service-list | grep ec2

It was for compatibility's reason that Heat uses EC2 token authentication for 
the alarm url, as I have mentioned in previous replies.

Regards,
  Qiming

On Tue, Mar 10, 2015 at 01:44:17PM +, Chinasubbareddy M wrote:
> Hi,
> 
> We used to have Ip address only , while troubleshooting we made that to 
> localhost.
> If you see the url , there is AWS access key and if we execute the url 
> manually , its getting failed to contact keystone and get token.
> 
> If we get the token manually and request it again ,it's getting failed with 
> unknown heat resource.
> 
> It would be easy if you can share any working template which is generating 
> proper webhook.
> 
> 
> Regards,
> Subbareddy,
> Persistent systems.
> 
> 
> 
> -Original Message-
> From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com]
> Sent: Wednesday, March 11, 2015 3:00 AM
> To: openstack@lists.openstack.org
> Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]
> 
> Checked your alarm_url string again, it seems that your heat.conf file 
> contains this line:
> 
> heat_waitcondition_server_url=http://:8000/waitcondition
> 
> You have to change  to the IP of the heat-cfn-api service host.
> 
> Regards,
>  Qiming
> 
> On Tue, Mar 10, 2015 at 10:47:10AM +, Srujana C P wrote:
> > Hi,
> >
> > I would like to explore on auto scaling functionality of heat. So I 
> > have started with sample word press template available. It could 
> > create a stack(alarms, instance, etc., ). However, alarm is not 
> > getting triggered whenever I put stress on it. The alarm_action 
> > assigned to the alarm created from the template is Alarm_action :
> > http://:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a
> > 7c 
> > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > 2c 
> > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2 > :/ 
> > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > 4b
> > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > 13 
> > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > OT 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D
> >
> > This alarm_url is not d

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

[chinasubbareddy m]

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.driver [-] Unable to load the
virtualization driver
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver Traceback (most recent
call last):
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
"/usr/lib/python2.7/dist-packages/nova/virt/driver.py", line 1389, in
load_compute_driver
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver virtapi)
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
"/usr/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 52, in
import_object_ns
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver return
import_class(import_str)(*args, **kwargs)
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
"/usr/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 27, in
import_class
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver __import__(mod_str)
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver ImportError: No module
named libvirt
2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][kilo][compute_driver]

[chinasubbareddy m]

Hi,

problem was openstack installation auto detecting the hypervisor type and
installing the compute driver accordingly.

since i am running my vm in my laptop on vmware player ,compute driver got
installed was vmware, but i would like to install libvirt driver.

Here is the error if i try to install nova-compute-kvm:

root@kiloos:~# apt-get install nova-compute-kvm sysfsutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nova-compute-kvm : Depends: nova-compute-libvirt (=
1:2015.1.0-0ubuntu1~cloud0) but it is not going to be installed
Depends: qemu-system (>= 1.3.0) or
 kvm
E: Unable to correct problems, you have held broken packages.



On Mon, Jun 8, 2015 at 11:36 AM, chinasubbareddy m <
subbareddy.openst...@gmail.com> wrote:

> 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.driver [-] Unable to load
> the virtualization driver
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver Traceback (most
> recent call last):
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
> "/usr/lib/python2.7/dist-packages/nova/virt/driver.py", line 1389, in
> load_compute_driver
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver virtapi)
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 52, in
> import_object_ns
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver return
> import_class(import_str)(*args, **kwargs)
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 27, in
> import_class
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver
> __import__(mod_str)
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver ImportError: No
> module named libvirt
> 2015-06-08 17:04:53.155 16600 TRACE nova.virt.driver
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][kilo][vm launch error][libvirt]libvirtError: invalid argument: monitor must not be NULL

[chinasubbareddy m]

Hi,

if i try to launch a VM in kilo , getting error like below, help me out.


/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
rv = execute(f, *args, **kwargs)
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in
execute
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
six.reraise(c, e, tb)
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 80, in
tworker
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
rv = meth(*args, **kwargs)
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 896, in
createWithFlags
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
libvirtError: invalid argument: monitor must not be NULL
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.013 10436 TRACE
nova.compute.manager [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36]
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.017 10436 INFO
nova.compute.manager [req-48e78c5c-af08-4747-ab06-b341aeaeb7f5
ae5a2fa391b94dd69237f5af0aa98f87 f43823aa776c4880b5543c78a58fe4ab - - -]
[instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] Terminating instance
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.033 10436 INFO
nova.virt.libvirt.driver [-] [instance:
3a286da5-a3ac-428d-9a7b-9f05e3122d36] Instance destroyed successfully.
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.053 10436 INFO
nova.virt.libvirt.driver [req-cfba2b58-760c-42de-a04a-d877b815a6ca - - - -
-] [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] Deleting instance files
/var/lib/nova/instances/3a286da5-a3ac-428d-9a7b-9f05e3122d36_del
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.055 10436 INFO
nova.virt.libvirt.driver [req-cfba2b58-760c-42de-a04a-d877b815a6ca - - - -
-] [instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] Deletion of
/var/lib/nova/instances/3a286da5-a3ac-428d-9a7b-9f05e3122d36_del complete
/var/log/nova/nova-compute.log:2015-06-11 08:27:47.261 10436 INFO
nova.compute.manager [req-045d0698-0a10-4b75-86d0-e41a798749a4 - - - - -]
[instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] During sync_power_state
the instance has a pending task (spawning). Skip.
/var/log/nova/nova-conductor.log:2015-06-11 08:27:47.333 10537 ERROR
nova.scheduler.utils [req-48e78c5c-af08-4747-ab06-b341aeaeb7f5
ae5a2fa391b94dd69237f5af0aa98f87 f43823aa776c4880b5543c78a58fe4ab - - -]
[instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] Error from last host:
kiloctl (node kiloctl.hp.com): [u'Traceback (most recent call last):\n', u'
 File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line
2219, in _do_build_and_run_instance\nfilter_properties)\n', u'  File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2362, in
_build_and_run_instance\ninstance_uuid=instance.uuid,
reason=six.text_type(e))\n', u'RescheduledException: Build of instance
3a286da5-a3ac-428d-9a7b-9f05e3122d36 was re-scheduled: invalid argument:
monitor must not be NULL\n']
/var/log/nova/nova-conductor.log:2015-06-11 08:27:47.403 10537 WARNING
nova.scheduler.utils [req-48e78c5c-af08-4747-ab06-b341aeaeb7f5
ae5a2fa391b94dd69237f5af0aa98f87 f43823aa776c4880b5543c78a58fe4ab - - -]
[instance: 3a286da5-a3ac-428d-9a7b-9f05e3122d36] Setting instance to ERROR
state.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][opendaylight]

[chinasubbareddy m]

Hi,

could you please guide me good blogs for integrating  opeack and
opendaylight ?


Regards,
subbareddy.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][glance][ipv6]

[Chinasubbareddy M]

Hi,

I am setting up glance with icehouse on Ubuntu 14.o4, I am getting following 
error :

2014-05-12 21:38:31.223 19851 CRITICAL glance [-] gaierror: [Errno -3] 
Temporary failure in name resolution

2014-05-12 21:38:32.263 19863 ERROR glance.store.sheepdog [-] Error in store 
configuration: Unexpected error while running command.
Command: None
Exit code: -
Stdout: "Unexpected error while running command.\nCommand: collie vdi list -a 
2001:db8:1::20 -p 7000\nExit code: 2\nStdout: '  NameIdSizeUsed 
 SharedCreation time   VDI id  Copies  Tag\\n'\nStderr: 'failed to connect 
to 2001:db8:1::20:7000: Connection refused\\nfailed to connect to 
2001:db8:1::20:7000: Connection refused\\n'"
Stderr: None


I am able to run keystone successfully with ipv6 and also be able to ping6 to 
the address successfully, but getting this error when I am starting the glance 
,please suggest.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][glance][ipv6]

[Chinasubbareddy M]

Thanks for the suggestion, followed the same document but the problem still 
exists .
This is the main issue.

Stdout: "Unexpected error while running command.\nCommand: collie vdi list -a 
build-node -p 7000\nExit code: 1\nStdout: ''\nStderr: 'Invalid ip address 
build-node\\n'"



From: Martinx - ジェームズ [mailto:thiagocmarti...@gmail.com]
Sent: Monday, May 12, 2014 10:35 PM
To: Chinasubbareddy M
Cc: openstack@lists.openstack.org; Ram Nalluri; Boddepalli Srikanth
Subject: Re: [Openstack] [openstack][glance][ipv6]

Hello!

I'm running Glance over IPv6, here is my Quick Guide (it follows 
docs.openstack.org<http://docs.openstack.org>):

---
Ultimate OpenStack IceHouse Guide - ML2 Flat Network - IPv6-Friendly:
https://gist.github.com/tmartinx/9177697
---

Also, keep in mind that this IPv6 subnet (2001:db8:), is used only for 
documentation purposes, this means that it will not get routed (by 
upstream/ISP/wifi routers), so, to test with it, you must try from within it... 
Or, replace it with your own IPv6 subnet to test from the Internet.

Hope it helps!

Best,
Thiago

On 12 May 2014 13:16, Chinasubbareddy M 
mailto:chinasubbaredd...@persistent.co.in>> 
wrote:
Hi,

I am setting up glance with icehouse on Ubuntu 14.o4, I am getting following 
error :

2014-05-12 21:38:31.223 19851 CRITICAL glance [-] gaierror: 
[Errno -3] Temporary failure in name resolution

2014-05-12 21:38:32.263 19863 ERROR glance.store.sheepdog 
[-] Error in store configuration: Unexpected error while running command.
Command: None
Exit code: -
Stdout: "Unexpected error while running command.\nCommand: collie vdi list -a 
2001:db8:1::20 -p 7000\nExit code: 2\nStdout: '  NameIdSizeUsed 
 SharedCreation time   VDI id  Copies  Tag\\n'\nStderr: 'failed to connect 
to 2001:db8:1::20:7000: Connection refused\\nfailed to connect to 
2001:db8:1::20:7000: Connection refused\\n'"
Stderr: None


I am able to run keystone successfully with ipv6 and also be able to ping6 to 
the address successfully, but getting this error when I am starting the glance 
,please suggest.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] curl call to list servers in a specified region

[Chinasubbareddy M]

Hi,


I would like to know the curl request for listing the servers within a 
specified region, region should be mentioned in the curl request only, please 
suggest.



Regards,

Subbareddy.


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Inconsistent official docs for enabling LBaas and Fwaas

[Chinasubbareddy M]

Hi,

I have configured both of them and it was working fine in Havana.

Here is the way I mentioned in config file ,

# Advanced service modules
# service_plugins =
service_plugins = neutron.services.loadbalancer.plugin.LoadBalancerPlugin
service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin

From: Xianyi Ye [mailto:yexia...@sina.com]
Sent: Wednesday, July 23, 2014 2:19 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Inconsistent official docs for enabling LBaas and Fwaas

Hi all,

Is there anyone knows how to enable LBaas and Fwaas simultaneously?
Currently, I'm totally confused by 2 different config doc.

One is from 
http://docs.openstack.org/admin-guide-cloud/content/install_neutron-fwaas-agent.html
 which told me to modify neutron.conf as below.
service_plugins = firewall

Another doc from https://wiki.openstack.org/wiki/Neutron/FWaaS/HowToInstall 
which told me to change same attribute with
service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin

The thing confused me is why these 2 official docs instruct me to change the 
same parameter, 'service_plugins', with 2 absolutely different values and 
formats.

Dos Openstack support both of these 2 formats at a same time? If not, which 
instruction is correct?

Thanks for any help!
Xianyi Ye

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] router cannot communicate with external

[Chinasubbareddy M]

Hi,

Can you please share the routes at router and instance ,

ip netns exec qrouter-e3119ff4-2fac-4226-9e63-009cfce8ac4c route -n
also share the route of qdhcp and the instance.

Regards,
Subbareddy,
Persistent systems ltd.

From: ZHOU TAO A [mailto:tao.a.z...@alcatel-lucent.com]
Sent: Thursday, July 24, 2014 8:26 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] router cannot communicate with external


Hi,

I have installed icehouse with ovs vlan configuration.
Network node and controller node coexists.

The problem is I can ping the public IP address of my router but cannot ping 
external gateway from my instance.

My instance has internal IP 192.48.1.51 and a floating IP 135.252.167.187. My 
router has subnet 192.48.1.0/24 and gateway 135.252.167.186

[root@ih-controller neutron]# ip netns exec 
qrouter-e3119ff4-2fac-4226-9e63-009cfce8ac4c ping 135.252.167.1
PING 135.252.167.1 (135.252.167.1) 56(84) bytes of data.
>From 135.252.167.186 icmp_seq=2 Destination Host Unreachable
>From 135.252.167.186 icmp_seq=3 Destination Host Unreachable
>From 135.252.167.186 icmp_seq=4 Destination Host Unreachable



[root@ih-controller neutron]# neutron router-list
+--++-+
| id   | name   | external_gateway_info 
  |
+--++-+
| e3119ff4-2fac-4226-9e63-009cfce8ac4c | router_ext | {"network_id": 
"0b78bc26-0374-47ed-8f0b-66d18e3bd86b", "enable_snat": true} |
+--++-+

ip netns exec qrouter-e3119ff4-2fac-4226-9e63-009cfce8ac4c ifconfig
loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:0
  TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:448 (448.0 b)  TX bytes:448 (448.0 b)

qg-256b404e-50 Link encap:Ethernet  HWaddr FA:16:3E:2A:D3:D0
  inet addr:135.252.167.186  Bcast:135.252.167.255  Mask:255.255.255.0
  inet6 addr: fe80::f816:3eff:fe2a:d3d0/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:191469 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1293 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:16274751 (15.5 MiB)  TX bytes:123922 (121.0 KiB)

qr-c87773a3-79 Link encap:Ethernet  HWaddr FA:16:3E:03:42:C3
  inet addr:192.48.1.254  Bcast:192.48.1.255  Mask:255.255.255.0
  inet6 addr: fe80::f816:3eff:fe03:42c3/64 Scope:Link
  UP BROADCAST RUNNING  MTU:1500  Metric:1
  RX packets:1286 errors:0 dropped:0 overruns:0 frame:0
  TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:124478 (121.5 KiB)  TX bytes:1986 (1.9 KiB)



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] issue with multiple floating ip pools for neutron network

[Chinasubbareddy M]

Hi,


What about  the handle_internal_only_routers option ?



You need to make sure one should be true and remaining should be false like ,



For the first agent


handle_internal_only_routers = True

gateway_external_network_id = 2118b11c-011e-4fa5-a6f1-2ca34d372c35

external_network_bridge = br-ex

For the second (or later) agent


handle_internal_only_routers = False

gateway_external_network_id = e828e54c-850a-4e74-80a8-8b79c6a285d8

external_network_bridge = br-ex-2



Before starting L3 agents, you need to create routers and external networks, 
then update the configuration files with UUID of external networks and start L3 
agents.



Regards,

Subbareddy,

Persistent systems ltd.


From: Zhi-Wei Lu [mailto:z...@ucdavis.edu]
Sent: Monday, July 28, 2014 10:43 PM
To: openstack@lists.openstack.org
Subject: [Openstack] issue with multiple floating ip pools for neutron network

Hi all,

I have been testing multiple floating ip pools with neutron network on CentOS 
6.5 with icehouse.  The single floating ip pool set up worked fine, but I 
encountered many problems setting up multiple floating IP pools.  I now enabled 
l3-agent with empty string (in /etc/neutron/l3-agent.ini) for multiple
gateway_external_network_id =
external_network_bridge =

The external bridges, br-ex and br-ex2, do not have the qg-* port at all, these 
qg-* interfaces are now in the br-int, therefore the floating ips do not work 
anymore.  Is there any way to move "qg" port from br-int to br-ex, and br-ex2?  
I don't know how I ended up with such a mess, do I have to remove the network 
set up and reconfigure neutron?

Thank you very much for your help.

Zhi-Wei Lu
IET-CR-Network Operations Center
University of California, Davis
(530) 752-0155


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack networking usecase

[Chinasubbareddy M]

Hi,

Please go through this link ,please revert if you have any issues.

https://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks/

From: Ramprasad Velavarthipati [mailto:rampras...@gmail.com]
Sent: Thursday, August 07, 2014 2:45 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack networking usecase

Hello All,

I need your help in following networking scenario:


  *   I bring up 2 VM's in a compute Node via Openstack Controller Dashboard
  *   these two VM's below to same virtual Network
  *   Each VM gets an virtual IP address
  *   SCENARIO: Is it possible that, each virtual IP is given assigned an 
access-vlan and pass the vlan traffic to outside physical/real port that is 
connected to Trunk port of an external switch?
  *   VM1 and VM2 shouldnt talk to each other without passing through the trunk 
port

Example:
VM1 gets a virtual IP address lets say 10.0.0.20/24., how 
to assign a access vlan, lets say vlan 10.,

VM2 gets a virtual  IP address lets say 10.10.0.20/24.,  
how to assign a access vlan, lets say vlan20(access port)

My physical interface of the compute node is ETH0., connected to trunk port of 
a switch.,

VM1 and VM2 shouldnt talk to each other until and unless they pass through the 
trunk and gets the packet processed further by an external l3 switch..

does it require an explicit configuration of openVswitch ??

--
Thanks,
-Ram

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Template for wordpress

[Chinasubbareddy M]

Hi ,

You can mention default network inside the template itself  or can   pass as a 
parameter  while creating the stack.
Here is the example ,



As parameter:

heat stack-create  -f  /root/rsoft-intall.yaml 
--parameters="server_name=r1m5;key_name=test;flavor=m1.small;image=aaf91618-ed6e-48e4-a6cc-e6f74dc6c82d;private_net_id=25993771-5cdf-4e66-84dd-a6c19d932e0d"
 wp-stack5

Note: you should give network id not name of the network.



Inside template:


private_net_id:
type: string
description: ID of private network into which servers get deployed

networks:
- port: { get_resource: my_instance_port }

  my_instance_port:
type: OS::Neutron::Port
properties:
  network_id: { get_param: private_net_id }


regards,
subbareddy
persistent systems ltd.

From: yalla.gnan.ku...@accenture.com [mailto:yalla.gnan.ku...@accenture.com]
Sent: Thursday, September 04, 2014 5:50 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Template for wordpress

Hi All,

I am trying to implement autoscaling using the template attached for multiple 
neutron networks.
While creating the server in the webservergroup,   it is failing by showing the 
below error :

--
web_server_group   | c6189de2-d748-44f2-9b60-0d2e708e1d1f | Error: Resource 
CREATE failed: Error: Resource CREATE failed: BadRequest: Multiple possible 
networks found



I have attached the template to this mail.   Please check it and  let me know 
how to specify  a network ID in the websergroup   .


Thanks
Kumar



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy.
__

www.accenture.com

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] ICehouse[Neutron][ML2][VLAN] - nova boot failed

[Chinasubbareddy M]

Hi ,

When I am configuring ML2 plugin with vlan based network ,  nova boot is 
failing with following error ,where as if I change the driver from ML2 to OVS  
, things are working fine .
Please suggest.


Here is the ml2 configuration:

[ml2]
type_drivers = vlan
tenant_network_types = vlan
mechanism drivers = openvswitch
[ml2_type_vlan]
network_vlan_ranges = physnet1:1:4094
[ovs]
tenant_network_type = vlan
network_vlan_ranges = physnet1:1:4094
bridge_mappings = physnet1:eth1
[securitygroup]
firewall_driver = 
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
enable_security_group = True

/etc/neutron/neutron.conf:
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True


logs:


root@build-server:/etc/init# grep -ir "241e4c21-5604-4a1b-a782-f44128fbd0b3" 
/var/log/nova/*
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 ERROR 
nova.compute.manager [req-f4550d18-b37c-4dc6-9544-a9e8b2e38821 
5249dfc7f6c34fe68f98cfe60f82b331 22ad3f28f8f24b7fb14f17af44aa55f0] [instance: 
241e4c21-5604-4a1b-a782-f44128fbd0b3] Instance failed to spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] Traceback 
(most recent call last):
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2250, in 
spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
write_to_disk=True)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3431, in 
to_xml
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
disk_info, rescue, block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3247, in 
get_guest_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
flavor)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in 
get_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
_("Unexpected vif_type=%s") % vif_type)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
NovaException: Unexpected vif_type=binding_failed
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.877 21941 ERROR 
nova.virt.libvirt.driver [-] [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
During wait destroy, instance disappeared.
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 ERROR 
nova.compute.manager [req-f4550d18-b37c-4dc6-9544-a9e8b2e38821 
5249dfc7f6c34fe68f98cfe60f82b331 22ad3f28f8f24b7fb14f17af44aa55f0] [instance: 
241e4c21-5604-4a1b-a782-f44128fbd0b3] Error: Unexpected vif_type=binding_failed
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] Traceback 
(most recent call last):
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1311, in 
_build_instance
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
set_access_ip=set_access_ip)
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 399, in 
decorated_function
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance

Re: [Openstack] ICehouse[Neutron][ML2][VLAN] - nova boot failed

[Chinasubbareddy M]

Hi,

Thanks for your support ,changed the configuration ,still problem persist.
Do you have any working  vlan,ml2 plugin configuration? If you have Please 
share.

My understanding is, by the time request goes to vifdriver.py , viftype  
variable should be 'ovs' , but that is not happening in case of ml2 plugin.
Hope ml2 plugin not able to provide that information.
Do I need to do any changes in nova.conf in case of ml2?

From: Gangur, Hrushikesh (R & D HP Cloud) [mailto:hrushikesh.gan...@hp.com]
Sent: Thursday, September 11, 2014 11:22 AM
To: Chinasubbareddy M; openstack@lists.openstack.org
Cc: Ayyalaraju Koundinya; Ram Nalluri
Subject: RE: ICehouse[Neutron][ML2][VLAN] - nova boot failed

Shouldn't this be physnet1:br-eth1

>>>bridge_mappings = physnet1:eth1

Create a bridge named br-eth1 with eth1 as port on both controller and compute 
nodes
ovs-vsctl add-br br-eth1
ovs-vsctl add-port br-eth1 eth1



From: Chinasubbareddy M [mailto:chinasubbaredd...@persistent.co.in]
Sent: Wednesday, September 10, 2014 9:27 AM
To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Cc: Ayyalaraju Koundinya; Ram Nalluri
Subject: [Openstack] ICehouse[Neutron][ML2][VLAN] - nova boot failed

Hi ,

When I am configuring ML2 plugin with vlan based network ,  nova boot is 
failing with following error ,where as if I change the driver from ML2 to OVS  
, things are working fine .
Please suggest.


Here is the ml2 configuration:

[ml2]
type_drivers = vlan
tenant_network_types = vlan
mechanism drivers = openvswitch
[ml2_type_vlan]
network_vlan_ranges = physnet1:1:4094
[ovs]
tenant_network_type = vlan
network_vlan_ranges = physnet1:1:4094
bridge_mappings = physnet1:eth1
[securitygroup]
firewall_driver = 
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
enable_security_group = True

/etc/neutron/neutron.conf:
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True


logs:


root@build-server:/etc/init# grep -ir "241e4c21-5604-4a1b-a782-f44128fbd0b3" 
/var/log/nova/*
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 ERROR 
nova.compute.manager [req-f4550d18-b37c-4dc6-9544-a9e8b2e38821 
5249dfc7f6c34fe68f98cfe60f82b331 22ad3f28f8f24b7fb14f17af44aa55f0] [instance: 
241e4c21-5604-4a1b-a782-f44128fbd0b3] Instance failed to spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] Traceback 
(most recent call last):
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2250, in 
spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
write_to_disk=True)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3431, in 
to_xml
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
disk_info, rescue, block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3247, in 
get_guest_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
flavor)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in 
get_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
_("Unexpected vif_type=%s") % vif_type)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
NovaException: Unexpected vif_type=binding_failed
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.877 21941 ERROR 
nova.virt.libvir

[Openstack] [openstack][swift]-container mount into ubuntu

[Chinasubbareddy M]

Hi,

Do we have any facility like s3fs to mount swift container into our local  
server?
I am trying to use cloud-fuse but facing some issues ,please let me know if you 
are successfully mounted  swift container with cloud-fuse.

Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [keystone][multi-region][project-quota]

[Chinasubbareddy M]

Hi,

In a deployment scenario where one keystone has several regions registered, how 
the project quota are managed by, as an example, two nova services in two 
different regions?

I am wondering if is it possible to set quota on the project for all regions or 
this must to be done on a region by region basis which really means a quota for 
a project in a region.

Thanks in advance,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [Heat][multi-region]

[Chinasubbareddy M]

Hi,

I would like to use Heat to create/update and delete resources in different 
regions, can you please guide me how to mention it in template?

Regards,
subbareddy

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstacl][neutron][ml2][vlan]

[Chinasubbareddy M]

Hi ,

When I am configuring ML2 plugin with vlan based network ,  nova boot is 
failing with following error ,where as if I change the driver from ML2 to OVS  
, things are working fine .
Please suggest.


Here is the ml2 configuration:

[ml2]
type_drivers = vlan
tenant_network_types = vlan
mechanism drivers = openvswitch
[ml2_type_vlan]
network_vlan_ranges = physnet1:1:4094
[ovs]
tenant_network_type = vlan
network_vlan_ranges = physnet1:1:4094
bridge_mappings = physnet1:br-eth1
[securitygroup]
firewall_driver = 
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
enable_security_group = True

/etc/neutron/neutron.conf:
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = True


logs:


root@build-server:/etc/init# grep -ir "241e4c21-5604-4a1b-a782-f44128fbd0b3" 
/var/log/nova/*
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 ERROR 
nova.compute.manager [req-f4550d18-b37c-4dc6-9544-a9e8b2e38821 
5249dfc7f6c34fe68f98cfe60f82b331 22ad3f28f8f24b7fb14f17af44aa55f0] [instance: 
241e4c21-5604-4a1b-a782-f44128fbd0b3] Instance failed to spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] Traceback 
(most recent call last):
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2250, in 
spawn
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
write_to_disk=True)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3431, in 
to_xml
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
disk_info, rescue, block_device_info)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3247, in 
get_guest_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
flavor)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in 
get_config
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
_("Unexpected vif_type=%s") % vif_type)
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
NovaException: Unexpected vif_type=binding_failed
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.053 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]
/var/log/nova/nova-compute.log:2014-09-11 02:41:23.877 21941 ERROR 
nova.virt.libvirt.driver [-] [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
During wait destroy, instance disappeared.
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 ERROR 
nova.compute.manager [req-f4550d18-b37c-4dc6-9544-a9e8b2e38821 
5249dfc7f6c34fe68f98cfe60f82b331 22ad3f28f8f24b7fb14f17af44aa55f0] [instance: 
241e4c21-5604-4a1b-a782-f44128fbd0b3] Error: Unexpected vif_type=binding_failed
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] Traceback 
(most recent call last):
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1311, in 
_build_instance
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3] 
set_access_ip=set_access_ip)
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [instance: 241e4c21-5604-4a1b-a782-f44128fbd0b3]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 399, in 
decorated_function
/var/log/nova/nova-compute.log:2014-09-11 02:41:24.275 21941 TRACE 
nova.compute.manager [insta

[Openstack] [icehouse][HA]

[Chinasubbareddy M]

Hi,

I have a requirement to install openstack icehouse HA setup with 10 nodes 
running Ubuntu 14.04 operating system.
Please suggest a suitable deployment tool for the above requirement. Any 
documents or url's would be helpful.


Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

[Chinasubbareddy M]

Hi,


1.   I have successfully configured floating ips  in neutron and everything 
working fine , but as per the docs there should be int-br-ex and phy-br-int  
veth pair should be created  between br-int and br-ex, but  that  is not 
created in my setup ,floating ip are working fine, Please suggest .

2.   Added one of my nic which has connected to trunk port of switch to 
br-ex , I would like create multiple external networks and use each one for 
them for different  tenants or if different tenants wants to create their own 
floating ip networks ,what is the solution?

Issues I am facing here are:



I . if I add multiple subnets to external network , how to create floating ip 
from specific subnet?

Ii . can I create multiple external networks with single L3 agent?

iii.  should I create virtual interfaces like eth2.23(23 is vlan)  and add them 
to br-ex for each vlan?

Correct me if  I am wrong in understanding  floating ip networks in neutron.


Here is my ovs-vsctl output:

ovs-vsctl show
f85c99e8-7423-42da-879e-8d4e3f79c7f2
Bridge br-ex
Port "em3.29"
Interface "em3.29"
Port "qg-01b3854d-fa"
Interface "qg-01b3854d-fa"
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge "br-eth1"
Port "phy-br-eth1"
Interface "phy-br-eth1"
Port "br-eth1"
Interface "br-eth1"
type: internal
Port "em2"
Interface "em2"
Bridge br-int
Port "qr-b70d92cb-cd"
tag: 2
Interface "qr-b70d92cb-cd"
type: internal
Port "qvoa239a290-cf"
tag: 2
Interface "qvoa239a290-cf"
Port br-int
Interface br-int
type: internal
Port "tapfaa69064-de"
tag: 5
Interface "tapfaa69064-de"
type: internal
Port "int-br-eth1"
Interface "int-br-eth1"
Port "qvo9bce9829-2a"
tag: 5
Interface "qvo9bce9829-2a"
Port "tapd3e11080-82"
tag: 2
Interface "tapd3e11080-82"
type: internal

regards,
subbareddy,
persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

[Chinasubbareddy M]

Thank you so much  of your clarification james.
Can you please guide me for my second question that I asked in the mail?
If each tenant wants to create their own floating ip networks , what is the 
best design?

From: James Denton [mailto:james.den...@rackspace.com]
Sent: Thursday, October 16, 2014 11:12 PM
To: Chinasubbareddy M; openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

Subbareddy,

The external bridge (br-ex), when set, is used only for the external (qg) port 
of the router AFAIK and does not need to connect to br-int. The internal 
interface of the router (qr) is connected to the integration bridge. If 
floating IPs are working ok, and your router is properly routing traffic to 
instances, then your configuration is working properly as-is. A provider 
bridge, like br-eth1, would connect to the integration bridge via a patch port 
as you've described.

James

From: Chinasubbareddy M 
mailto:chinasubbaredd...@persistent.co.in>>
Date: Thursday, October 16, 2014 at 11:58 AM
To: "openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>" 
mailto:openstack@lists.openstack.org>>
Subject: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

Hi,


1.   I have successfully configured floating ips  in neutron and everything 
working fine , but as per the docs there should be int-br-ex and phy-br-int  
veth pair should be created  between br-int and br-ex, but  that  is not 
created in my setup ,floating ip are working fine, Please suggest .

2.   Added one of my nic which has connected to trunk port of switch to 
br-ex , I would like create multiple external networks and use each one for 
them for different  tenants or if different tenants wants to create their own 
floating ip networks ,what is the solution?

Issues I am facing here are:



I . if I add multiple subnets to external network , how to create floating ip 
from specific subnet?

Ii . can I create multiple external networks with single L3 agent?

iii.  should I create virtual interfaces like eth2.23(23 is vlan)  and add them 
to br-ex for each vlan?

Correct me if  I am wrong in understanding  floating ip networks in neutron.


Here is my ovs-vsctl output:

ovs-vsctl show
f85c99e8-7423-42da-879e-8d4e3f79c7f2
Bridge br-ex
Port "em3.29"
Interface "em3.29"
Port "qg-01b3854d-fa"
Interface "qg-01b3854d-fa"
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge "br-eth1"
Port "phy-br-eth1"
Interface "phy-br-eth1"
Port "br-eth1"
Interface "br-eth1"
type: internal
Port "em2"
Interface "em2"
Bridge br-int
Port "qr-b70d92cb-cd"
tag: 2
Interface "qr-b70d92cb-cd"
type: internal
Port "qvoa239a290-cf"
tag: 2
Interface "qvoa239a290-cf"
Port br-int
Interface br-int
type: internal
Port "tapfaa69064-de"
tag: 5
Interface "tapfaa69064-de"
type: internal
Port "int-br-eth1"
Interface "int-br-eth1"
Port "qvo9bce9829-2a"
tag: 5
Interface "qvo9bce9829-2a"
Port "tapd3e11080-82"
tag: 2
Interface "tapd3e11080-82"
type: internal

regards,
subbareddy,
persistent systems ltd.

DISCLAIMER == This e-mail may contain privileged and confidential 
information which is the property of Persistent Systems Ltd. It is intended 
only for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Persistent Systems Ltd. does not accept any liability for virus infected mails.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

[Chinasubbareddy M]

Thank you James, will try the br-int  as external bridge and let you know.


From: James Denton [mailto:james.den...@rackspace.com]
Sent: Friday, October 17, 2014 10:13 PM
To: Chinasubbareddy M
Cc: James Denton; openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

Subbareddy,

Added one of my nic which has connected to trunk port of switch to br-ex , I 
would like create multiple external networks and use each one for them for 
different  tenants or if different tenants wants to create their own floating 
ip networks ,what is the solution?

Tenants are not able to create their own floating IP networks. That is handled 
by the administrator. A provider network needs the router:external attribute 
set to TRUE to be eligible as a floating pool.


Issues I am facing here are:

I . if I add multiple subnets to external network , how to create floating ip 
from specific subnet?

As far as I know, you can’t. Not sure about Juno, but in Havana there was no 
way to specify an address from the pool with the floatingip-create command. The 
address used would be the next available address. It will consume all addrs 
from the allocation range in subnet1, then move on to subnet2.


Ii . can I create multiple external networks with single L3 agent?

Yes, starting with Icehouse. There is no special configuration as far as i 
know. You can have multiple provider networks with router:external set to true.


iii.  should I create virtual interfaces like eth2.23(23 is vlan)  and add them 
to br-ex for each vlan?

You will not want to add multiple interfaces to the br-ex bridge if that’s what 
you’re using, as you would then bridge all of the vlans. Rather than using a 
hard-defined bridge in the l3_agent.ini, set set external_network_bridge to 
‘br-int’ or just leave it blank. For every floating pool you want to create, 
use the net-create/subnet-create commands to create the networks and set 
router:external to true. Neutron will place both the qg and qr ports in the 
integration bridge, and leverage the corresponding provider bridge you 
specified in net-create.

When tenants create their router and use router-gateway-set to attach to one of 
the networks you created, Neutron will connect the router ports to br-int, set 
the internal vlan accordingly on each port, and build the corresponding flows 
on the integration and provider bridges.

The idea is to leverage OVS to do the VLAN tagging for you, so don’t put 
eth2.23 in the bridge - put eth2 in the provider bridge and specify VLAN 23 as 
the segmentation Id in the net-create command. You can leverage the same 
provider bridge for multiple VLANs when OVS does the tagging.

Hope that helps.

James




Correct me if  I am wrong in understanding  floating ip networks in neutron.


On Oct 16, 2014, at 8:05 PM, Chinasubbareddy M 
mailto:chinasubbaredd...@persistent.co.in>> 
wrote:

Thank you so much  of your clarification james.
Can you please guide me for my second question that I asked in the mail?
If each tenant wants to create their own floating ip networks , what is the 
best design?

From: James Denton [mailto:james.den...@rackspace.com]
Sent: Thursday, October 16, 2014 11:12 PM
To: Chinasubbareddy M; 
openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Subject: Re: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

Subbareddy,

The external bridge (br-ex), when set, is used only for the external (qg) port 
of the router AFAIK and does not need to connect to br-int. The internal 
interface of the router (qr) is connected to the integration bridge. If 
floating IPs are working ok, and your router is properly routing traffic to 
instances, then your configuration is working properly as-is. A provider 
bridge, like br-eth1, would connect to the integration bridge via a patch port 
as you’ve described.

James

From: Chinasubbareddy M 
mailto:chinasubbaredd...@persistent.co.in>>
Date: Thursday, October 16, 2014 at 11:58 AM
To: "openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>" 
mailto:openstack@lists.openstack.org>>
Subject: [Openstack] [openstack][icehouse][neutron][floatingip][br-ex]

Hi,

1.   I have successfully configured floating ips  in neutron and everything 
working fine , but as per the docs there should be int-br-ex and phy-br-int  
veth pair should be created  between br-int and br-ex, but  that  is not 
created in my setup ,floating ip are working fine, Please suggest .
2.   Added one of my nic which has connected to trunk port of switch to 
br-ex , I would like create multiple external networks and use each one for 
them for different  tenants or if different tenants wants to create their own 
floating ip networks ,what is the solution?
Issues I am facing here are:

I . if I add multiple subnets to external network , how to create floating ip 
from specific subnet?
Ii . can I create multiple external networks wit

[Openstack] [icehouse][neutron]-Iptables

[Chinasubbareddy M]

Hi all,

I would like to know where the iptables at  compute side will get saved, I mean 
they will get saved in any configuration file or not.
When I change an iptable and restart the ovs agent , changes are going away and 
original iptables coming up.

I would like to understand deep into iPtables in opernstack ,please suggest me 
any working guides or blogs.

Regards,
Subbareddy,
Persistent systems ltd.
Hyderbad.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][glance][swift-backend][icehouse]

[Chinasubbareddy M]

Hi all,

I configured my glance backend to swift ,while uploading images to my glance am 
not able to upload files which are larger than 10GB, please help me out.
it is taking ages while uploading , please let me know if there are any changes 
which will improve the performance.

Regards,
Subbareddy,
Persistent systems ltd.


From: Chinasubbareddy M
Sent: Monday, November 24, 2014 10:51 PM
To: openstack@lists.openstack.org
Cc: Shanker Gudipati
Subject: [openstack][glance][swift-backend][icehouse]

Hi all,

I configured my glance backend to swift ,while uploading images to my glance am 
not able to upload files which are larger than 10GB, please help me out.
it is taking ages while uploading , please let me know if there are any changes 
which will improve the performance.

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][glance][swift-backend][icehouse]

[Chinasubbareddy M]

Hi,

When I am trying to upload 14 GB image , this is the issue I am getting:

2014-11-25 18:59:14.430 31680 TRACE swiftclient
2014-11-25 18:59:14.438 31680 ERROR glance.store.swift 
[3b26e687-0125-402b-a813-35e2c4d807fa 45e0ca2c6ef746458c4801cb0bb4c048 
22ff902721944cc592c0b4358698089b - - -] Failed to add object to Swift.
Got error from Swift: Object PUT failed: 
http://10.233.52.161:8080:8080/v1/AUTH_9bb0be211a254743be5e6d1497ca969d/glance/e27bb490-859b-429f-abda-664abd786d7c
 413 Request Entity Too Large  [first 60 chars of response] Request 
Entity Too LargeThe body of your r
2014-11-25 18:59:14.439 31680 ERROR glance.api.v1.upload_utils 
[3b26e687-0125-402b-a813-35e2c4d807fa 45e0ca2c6ef746458c4801cb0bb4c048 
22ff902721944cc592c0b4358698089b - - -] Failed to upload image 
e27bb490-859b-429f-abda-664abd786d7c
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils Traceback (most 
recent call last):
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.7/dist-packages/glance/api/v1/upload_utils.py", line 99, in 
upload_data_to_store
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils store)
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.7/dist-packages/glance/store/__init__.py", line 382, in 
store_add_to_backend
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils (location, 
size, checksum, metadata) = store.add(image_id, data, size)
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.7/dist-packages/glance/store/swift.py", line 503, in add
2014-11-25 18:59:14.439 31680 TRACE glance.api.v1.upload_utils raise 
glance.store.BackendException(msg)

From: Chinasubbareddy M
Sent: Tuesday, November 25, 2014 12:33 PM
To: 'openstack@lists.openstack.org'
Subject: RE: [openstack][glance][swift-backend][icehouse]

Hi all,

I configured my glance backend to swift ,while uploading images to my glance am 
not able to upload files which are larger than 10GB, please help me out.
it is taking ages while uploading , please let me know if there are any changes 
which will improve the performance.

Regards,
Subbareddy,
Persistent systems ltd.


From: Chinasubbareddy M
Sent: Monday, November 24, 2014 10:51 PM
To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>
Cc: Shanker Gudipati
Subject: [openstack][glance][swift-backend][icehouse]

Hi all,

I configured my glance backend to swift ,while uploading images to my glance am 
not able to upload files which are larger than 10GB, please help me out.
it is taking ages while uploading , please let me know if there are any changes 
which will improve the performance.

Regards,
Subbareddy,
Persistent systems ltd.

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack