[Openstack] Need help on neutron network device!!

[Sateesh Kolagani Kumar]

Hi,

I have enabled firewall in neutron.conf at controller (where neutron server 
installed) and Neutron node(where agents are installed)..after I create a 
firewall in dashboard its showing as PENDING_CREATE State not showing as 
active, all basic networking is working fine (used GRE tunnel). The changes 
made in Controller and neutron node..


Controller:

service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin

Neutron Node:


[fwaas]

driver = 
neutron.services.firewall.drivers.linux.iptables_fwaas.IptablesFwaasDriver

enabled = True

Is anything I am issuing here please suggest me.



Thanks and Regards,

Sateesh Kolagani



http://www.mindtree.com/email/disclaimer.html
___
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] Limit of tunnel_id_ranges in Neutron

[Changbin Liu]

Hi All,

Maybe this is a simple question: is there any limit on "tunnel_id_ranges"
in Neutron configuration? Say, can I configured it to e.g., "1:1" if I
have 1 tenants in the cloud. I know VLAN is limited to 4094 tags.

I googled around this issue but found that most commonly it  is configured
to default "1:1000".

Thanks

Changbin
___
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 Community Weekly Newsletter (Mar 21 – 28)

[Stefano Maffulli]

  OpenStack Summit May 2014 Schedule & Registration Deadlines
  


The official Summit agenda is now live*
. *Adjustments, edits,
additions to the schedule may be made between now and the Summit. 
Continue to visit the site for updates.
*March 28* is the last day to save 50% off the full price and register
for the Summit at the discounted Early Bird rate. Don’t miss out –
*prices will increase on March 29*. *Register now.
*


  Running a Baseline Usability Test on Horizon
  

Over the last few months, a group of folks from multiple companies has
been doing research around building a set of Personas

to present at the Atlanta Summit. Liz Blanchard
 wrote up the results of the
first usability testing 
on the most recent (Icehouse) version of the OpenStack Dashboard (Horizon).


The road to Juno Summit – Atlanta 2014

  * *Redeem* *your invite code NOW **or pay extra to join the Summit*!
Check your inbox and spam folder if you contributed code before
March 3^rd for your invitation.
  * No more batch invites will be sent.
  * Applying for Visa? Looking for accommodation in Atlanta? Visit
http://openstack.org/summit
  * Check the official agenda



  How to Build OpenStack Docs and Contributors through Community
  


Anne Gentle  lays the ground for the
discussions to be held in Atlanta: collaborate on a request for
proposals for a new front-end design for our documentation that can help
us make changes to how docs are authored. Also, how to enable non-CLA
contributors to the docs. Read more about our Docs team, how it manages
to work upstream and coordinate work across continents.


Security Advisories and Notices

  * [OSSA 2014-007] Potential context confusion in Keystone middleware
(CVE-2014-0105)


  * [OSSA 2014-008] Routers can be cross plugged by other tenants
(CVE-2014-0056)


  * [OSSA 2014-009] Nova host data leak to vm instance in rescue mode
(CVE-2014-0134)


  * [OSSN] DoS style attack on noVNC server can lead to service
interruption or disruption



Tips ‘n Tricks

  * By Matt Fischer : Keystone: User
Enabled Emulation Can Lead to Bad Performance

  * By Ben Nemec : Using
pypi-mirror with devtest



Upcoming Events

  * Open Source Festival
 Mar 29, 2014
– University at Albany, NY Details

  * Cloud Connect Summit at Interop
 Mar
31 – Apr 01, 2014 – Las Vegas, Nevada Details

  * OpenStack Today at the Percona Live MySQL Conference


Mar 31, 2014 – Santa Clara, CA Details


  * OpenStack for fools
 Apr 01,
2014 – London, United Kingdom Details

  * World Hosting Days Apr 01 –
03, 2014 – Rust, Germany Details 
  * SFBay Meetup – Beginner track
 Apr 03, 2014 –
Sunnyvale, CA Details

  * SFBay OpenStack Hackathon #OSSFO 
Apr 03, 2014 – Details 
  * OpenStack Nordics Meetup

Apr 03, 2014 – Stockholm, Sweden Details

  * PyCon 

Re: [Openstack] Getting Havana to work with Neutron, ML2 and VXLAN (vif_type=binding_failed error)

[Sławek Kapłoński]

Witam,

So You should check neutron server log (maybe with debug and verbose set to 
True). There should be information on which host there was attempt to bind 
port and why it fails.

--
Best regadrs
Sławek Kapłoński

Dnia piątek, 28 marca 2014 00:15:55 Tom Verdaat pisze:
> Thanks for your reply.
> 
> I checked that. Followed these
> instructions nstallation-and-configuration/?answer=7259#post-id-7259>too. Using the vxlan
> typedriver and openvswitch mechanism driver. Agents are up on both the
> networking node and compute node.
> 
> Pasted the agent information and configuration files below. vm-1 is the
> networking node, mv-4 the compute node. Tried configuring a public network
> for floating IP's but I get the same problem with a simple internal tenant
> network.
> 
> Any idea why it won't work?
> 
> Thanks,
> 
> Tom
> ---
> 
> # neutron agent-list
> +--++--+---+
> +
> | id   | agent_type | host | alive
> | admin_state_up |
> 
> +--++--+---+
> +
> | e3b5c1b3-307c-4c27-8ea2-30e253da776b | Loadbalancer agent | vm-1 | :-)
> | True   |
> | 8aa54d4a-27db-4ec9-a49f-0766479ce35c | Metering agent | vm-1 | :-)
> | True   |
> | e63e47c7-b78c-42b3-b28e-62e6ada26be2 | DHCP agent | vm-1 | :-)
> | True   |
> | 994c8598-ee7d-46ae-9681-b7718758199c | L3 agent   | vm-1 | :-)
> | True   |
> | c26c302c-19a1-44af-b941-061a11e559eb | Open vSwitch agent | vm-1 | :-)
> | True   |
> | d80bac01-f651-4ad3-8564-d6933ee9a919 | Open vSwitch agent | vm-4 | :-)
> | True   |
> 
> +--++--+---+
> +
> 
> 
> # neutron agent-show 994c8598-ee7d-46ae-9681-b7718758199c
> +-+-
> --+
> | Field   |
> 
> Value
> 
> +-+-
> --+
> | admin_state_up  |
> 
> True
> 
> | agent_type  | L3
> 
> agent  |
> | alive   |
> 
> True
> 
> | binary  |
> 
> neutron-l3-agent
> 
> | configurations  |
> 
> {
> 
> | |  "router_id":
> "", |
> 
> | |  "gateway_external_network_id":
> "",   |
> 
> | |  "handle_internal_only_routers":
> true,|
> 
> | |  "use_namespaces":
> true,  |
> 
> | |  "routers":
> 0,|
> 
> | |  "interfaces":
> 0, |
> 
> | |  "floating_ips":
> 0,   |
> 
> | |  "interface_driver":
> "neutron.agent.linux.interface.OVSInterfaceDriver",  |
> 
> | |  "ex_gw_ports":
> 0 |
> 
> }
> 
> | created_at  | 2014-03-27
> 
> 00:34:10.528993|
> 
> | description
> | 
> | 
> | heartbeat_timestamp | 2014-03-27
> 
> 09:47:34.777233|
> 
> | host|
> 
> vm-1
> 
> | id  |
> 
> 994c8598-ee7d-46ae-9681-b7718758199c
> 
> | started_at  | 2014-03-27
> 
> 08:47:30.366770|
> 
> | topic   |
> 
> l3_agent
> 
> +-+-
> --+
> 
> 
> # neutron agent-show c26c302c-19a1-44af-b941-061a11e559eb
> +-+--+
> 
> | Field   | Value|
> 
> +-+--+
> 
> | admin_state_up  | True |
> | agent_type  | Open vSwitch agent   |
> | alive   | True |
> | binary  | neutron-openvswitch-agent|
> | configurations  | {|
> | 
> | |  "tunnel_types": [   |
> | |  
> | |   "vxlan"|
> | |  
> | |  ],

[Openstack] POST and PUT ERROR IN SWIFT

[Ashish Dobhal]

Hello Everyone;
Please help me resolve the following errors in swift.
1.ERROR IN CREATING AN ACCOUNT
openswift@ubuntu:~/swift$ curl -i -H "X-Auth-Token:
AUTH_tk2e025cd645ba4fc9be084c7771a9066c " -X PUT
http://127.0.0.1:8080/v1/AUTH_batman
HTTP/1.1 403 Forbidden
Content-Length: 73
Content-Type: text/html; charset=UTF-8
X-Trans-Id: tx99b59668642a426a8c9f3-005335a3d6
Date: Fri, 28 Mar 2014 16:31:18 GMT

ForbiddenAccess was denied to this
resource.openswift@ubuntu:~/swift$ ^C
2.ERROR IN CREATING A CONTAINER

ERROR IN CREATING CONTAINER:
openswift@ubuntu:/$ swift --os-auth-token
AUTH_tk8e642119ea554ba39bb1cb3853e186dc \--os-storage-url
http://127.0.0.1:8080/v1/AUTH_test1 \post myluck
Container POST failed: http://127.0.0.1:8080/v1/AUTH_test1/myluck 403
Forbidden  [first 60 chars of response] ForbiddenAccess
was denied to this resourc


Thanks for your help.
___
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] Where should I report an issue w/ PackStack?

[Steve Gordon]

- Original Message -
> Hi there,
> 
> I ran into something similar when installing OS by hand following the
> RHEL/CentOS guide on openstack.org and using the RDO packages. Not 100% sure
> this is your problem on Packstack (as I didn't use Packstack), but maybe
> this helps.
> 
> If you look at the Keystone roles, I believe you will find the default member
> group is called "_member_". Horizon is looking for a group called "Member".
> 
> There is a parameter in horizon config file that if changed to "_member_"
> will fix the error your seeing.

In Icehouse Horizon was corrected to use "_member_" [1] which is what is used 
in the Keystone database creation/migration scripts since Grizzly, so this role 
always exists. It doesn't look like this has been backported to Havana though. 
My understanding of the current state in PackStack [2] is that it actually 
creates a "Member" role instead of overriding the Horizon configuration but it 
looks like this didn't occur in your case.

I'm wondering if PackStack was modified to stop creating the errant role before 
the Horizon change was brought into RDO?

Thanks,

Steve

[1] https://bugs.launchpad.net/horizon/+bug/1264228
[2] https://bugzilla.redhat.com/show_bug.cgi?id=984294


___
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] Ubuntu 12.04 Havana and ML2 plugin

[Atif Wasi]

Hi Folks,

I am sure this question have been asked before.  I have a small 3 node
OpenStack environment up and running with OVS plugin.  I want to start using
the ML2 plugin, but was not able to find where to download it from and how
to install/configure it.  Question is how to deploy the ML2 plugin on an
environment that is already up and running.

Thanks

AtifŠ.


___
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] Pip Error In Swift Installation (Swift All in One tutorial for a single node)

[Ashish Dobhal]

Hello,
I have successfully deployed swift using on a ubuntu VM.(Swift ALL in One
Installation).I have certain doubts.
1.difference bw -
*Authtoken andX os--token.*

*2. Is it possible to integrate the django swift browser with the swift. *
___
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] (no subject)

[Roman Kravets]

Adam,

I understend it, but I see that Swift always make object-replication for
all date on cluseter.
It make big load to hard drives on server.
Is it normal?

--
Best regards,
Roman Kravets


On Fri, Mar 28, 2014 at 5:29 AM, Adam Lawson  wrote:

> Swift is said to be eventually consistent because the data is stored then
> eventually distributed in a balanced way. You don't need to manually
> re-balance the rings constantly. Swift will do that for you. Re-balancing
> rings is usually initiated after you *change the ring structure*(add/remove 
> regions, add/remove zones, change device weights, etc).
>
> In your case since you only have one node, Swift will distribute the
> replicas across all 3 zones assuming you've configured 3x replication. When
> you add a node and update the rings, yes you'll want to re-balance. That
> will tell Swift to put a replica on the new node since Swift default
> behavior is to keep replica placements "as unique as possible". That's the
> actual Swift vernacular everyone uses. ; )
>
> Unique replica placement strategy is as follows:
>
> Region (if defined) > Zone > Node > Device > Device with fewest replicas
>
>
> Good luck.
>
> Adam
>
>
> *Adam Lawson*
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (888) 406-7620
>
>
>
> On Thu, Mar 27, 2014 at 12:48 PM, Roman Kravets  wrote:
>
>> Dear Adam,
>>
>> I have one storage server and 12 hard drives on it.
>> For test I split disk to 4 zones. If I rightly understood, swift load
>> date during "re-balance ring" and load data right away to correct node.
>>
>> --
>> Best regards,
>> Roman Kravets
>>
>>
>> On Thu, Mar 27, 2014 at 10:05 PM, Adam Lawson  wrote:
>>
>>> Probably has to do with the fact you (I'm guessing) don't have very many
>>> drives on that server. Is that a correct statement? I know that even with
>>> 50 drives across a cluster (still very small), rings balance is at 100%
>>> until the rings are adequately balanced. Look at your ring stats, drive
>>> count and 5 zones for more consistent reports.
>>>
>>>
>>> *Adam Lawson*
>>> AQORN, Inc.
>>> 427 North Tatnall Street
>>> Ste. 58461
>>> Wilmington, Delaware 19801-2230
>>> Toll-free: (888) 406-7620
>>>
>>>
>>>
>>> On Thu, Mar 27, 2014 at 10:20 AM, Кравец Роман wrote:
>>>
 Hello.

 I installed Openstack Swift to test server and upload 50 gb data.
 Now I see it in the log:
 root@storage1:/var/staff/softded# tail -n 1000 -f /var/log/syslog  |
 grep  replicated
 Mar 27 19:44:24 storage1 object-replicator 112746/187053 (60.27%)
 partitions replicated in 300.01s (375.81/sec, 3m remaining)
 Mar 27 19:47:44 storage1 object-replicator 187053/187053 (100.00%)
 partitions replicated in 499.71s (374.32/sec, 0s remaining)
 Mar 27 19:53:14 storage1 object-replicator 112863/187068 (60.33%)
 partitions replicated in 300.01s (376.20/sec, 3m remaining)
 Mar 27 19:56:29 storage1 object-replicator 187068/187068 (100.00%)
 partitions replicated in 494.53s (378.27/sec, 0s remaining)
 Mar 27 20:01:59 storage1 object-replicator 112343/187080 (60.05%)
 partitions replicated in 300.01s (374.47/sec, 3m remaining)
 Mar 27 20:05:18 storage1 object-replicator 187080/187080 (100.00%)
 partitions replicated in 498.55s (375.25/sec, 0s remaining)
 Mar 27 20:10:48 storage1 object-replicator 112417/187092 (60.09%)
 partitions replicated in 300.01s (374.71/sec, 3m remaining)

 Why object-replicator show different percent every time?

 Thank you!

 --
 Best regards,
 Roman Kravets

 ___
 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

[Openstack] ATC Reminder: Summit Registration

[Claire Massey]

Hi everyone,

Just a quick reminder that registration prices for the May 2014 OpenStack 
Summit in Atlanta will increase TODAY, March 28 at 11:55pm CST.  This is also 
the deadline for ATCs to register for the Summit for free.

We already provided all active technical contributors (ATCs) who contributed to 
the Havana release or Icehouse release (prior to March 7, 2014) with a USD 
$600-off discount code to register for a Full Access Pass to the Summit - this 
means that all ATCs can register for the Summit for FREE, but only if you use 
the code to register by 11:55pm CST TODAY.  If you use the ATC code to register 
after March 28 then a fee will be charged. 

When you register on EventBrite, you will need to enter your code before you 
select the Full Access level pass. It's easy to overlook, so please reference 
the following illustration: 
https://www.dropbox.com/s/durn7bgi3jatjeq/HowToUseCode_AtlantaSummit.png

REGISTER HERE-  https://openstacksummitmay2014.eventbrite.co.uk

Please email eve...@openstack.org with any Summit related questions.

Cheers,
Claire


___
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] Updation of binding:capabilities port filter for port failed using admin token in ML2 plugin

[Romil Gupta]

Hi All,


I am curious to understand the significance of binding:capabilities
{"port_filter": false}  in Neutron icehouse-2. The code reference is given
below :

https://github.com/openstack/neutron/blob/2014.1.b2/neutron/extensions/portbindings.py


 I created a port and tried to update the port_filter value :


*neutron port-update $Port_id --binding:capabilities type=dict
port_filter=true*

Error :  {'httperror': 'HTTP Error 400: Bad Request', u'NeutronError':
u'Cannot update read-only attribute binding:capabilities'}

Why admin is not allowed to update it ?

-- 
*Regards,*

*Romil *
___
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] Havana Installtion error

[Yitao Jiang]

Hi,Leon
i once got the same issue,solving them just by download source codes and
installed all dependencies using pip install -r REQUIREMENTS file.
 On Jan 14, 2014 3:44 PM, "Li, Leon (E-Lab)"  wrote:

> Pax,
>
>
>
> How did you fix the dependency issues? I have same issue.
>
>
> Leon
>
>
>
> *From:* Pax Mridhul [mailto:mrid...@live.com]
> *Sent:* 2013年11月16日 16:01
> *To:* openstack@lists.openstack.org
> *Subject:* [Openstack] Havana Installtion error
>
>
>
>
>
> Hello Friends,
>
>
>
> I’m trying to install Havana on my servers and seeing the following error
> while I’m trying to execute. Need some help on this.
>
>
>
> Link :
> http://docs.openstack.org/havana/install-guide/install/yum/content/keystone-install.html
>
>
>
> *[root@controller ~]# yum install openstack-keystone python-keystoneclient*
>
> Loaded plugins: priorities, product-id, refresh-packagekit, security,
> subscription-manager
>
> This system is registered to Red Hat Subscription Management, but is not
> receiving updates. You can use subscription-manager to assign subscriptions.
>
> 67 packages excluded due to repository priority protections
>
> Setting up Install Process
>
> Resolving Dependencies
>
> --> Running transaction check
>
> ---> Package openstack-keystone.noarch 0:2013.2-1.el6 will be installed
>
> --> Processing Dependency: python-keystone = 2013.2-1.el6 for package:
> openstack-keystone-2013.2-1.el6.noarch
>
> ---> Package python-keystoneclient.noarch 1:0.2.3-5.el6ost will be updated
>
> ---> Package python-keystoneclient.noarch 1:0.4.1-3.el6 will be an update
>
> --> Processing Dependency: python-babel for package:
> 1:python-keystoneclient-0.4.1-3.el6.noarch
>
> --> Running transaction check
>
> ---> Package python-keystone.noarch 0:2013.2-1.el6 will be installed
>
> --> Processing Dependency: python-oslo-config >= 1:1.2.0 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-dogpile-cache >= 0.5.0 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-babel >= 0.9.4 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-oauth2 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-lxml for package:
> python-keystone-2013.2-1.el6.noarch
>
> ---> Package python-keystoneclient.noarch 1:0.4.1-3.el6 will be an update
>
> --> Processing Dependency: python-babel for package:
> 1:python-keystoneclient-0.4.1-3.el6.noarch
>
> --> Running transaction check
>
> ---> Package python-dogpile-cache.noarch 0:0.5.0-1.el6 will be installed
>
> --> Processing Dependency: python-dogpile-core >= 0.4.1 for package:
> python-dogpile-cache-0.5.0-1.el6.noarch
>
> ---> Package python-keystone.noarch 0:2013.2-1.el6 will be installed
>
> --> Processing Dependency: python-babel >= 0.9.4 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-lxml for package:
> python-keystone-2013.2-1.el6.noarch
>
> ---> Package python-keystoneclient.noarch 1:0.4.1-3.el6 will be an update
>
> --> Processing Dependency: python-babel for package:
> 1:python-keystoneclient-0.4.1-3.el6.noarch
>
> ---> Package python-oauth2.noarch 0:1.5.211-5.el6 will be installed
>
> ---> Package python-oslo-config.noarch 1:1.1.0-3.el6ost will be updated
>
> ---> Package python-oslo-config.noarch 1:1.2.1-1.el6 will be an update
>
> --> Running transaction check
>
> ---> Package python-dogpile-core.noarch 0:0.4.1-1.el6 will be installed
>
> ---> Package python-keystone.noarch 0:2013.2-1.el6 will be installed
>
> --> Processing Dependency: python-babel >= 0.9.4 for package:
> python-keystone-2013.2-1.el6.noarch
>
> --> Processing Dependency: python-lxml for package:
> python-keystone-2013.2-1.el6.noarch
>
> ---> Package python-keystoneclient.noarch 1:0.4.1-3.el6 will be an update
>
> --> Processing Dependency: python-babel for package:
> 1:python-keystoneclient-0.4.1-3.el6.noarch
>
> --> Finished Dependency Resolution
>
> Error: Package: 1:python-keystoneclient-0.4.1-3.el6.noarch
> (openstack-havana)
>
>Requires: python-babel
>
> Error: Package: python-keystone-2013.2-1.el6.noarch (openstack-havana)
>
>Requires: python-babel >= 0.9.4
>
> Error: Package: python-keystone-2013.2-1.el6.noarch (openstack-havana)
>
>Requires: python-lxml
>
> You could try using --skip-broken to work around the problem
>
> You could try running: rpm -Va --nofiles --nodigest
>
>
>
>
>
> Output of the previous confiugurations :
>
> 
>
>
>
> Link :
> http://docs.openstack.org/havana/install-guide/install/yum/content/basics-packages.html
>
>
>
> *[root@controller ~]# yum install
> http://repos.fedorapeople.org/repos/openstack/openstack-havana/rdo-release-havana-6.noarch.rpm
> *
>
> Loaded plugins: priorities, product-id, refresh-packagekit, security,
> subscription-manager
>
> This system is registered to

Re: [Openstack] Where should I report an issue w/ PackStack?

[John Edrington]

Hi there, 

I ran into something similar when installing OS by hand following the 
RHEL/CentOS guide on openstack.org and using the RDO packages. Not 100% sure 
this is your problem on Packstack (as I didn't use Packstack), but maybe this 
helps. 

If you look at the Keystone roles, I believe you will find the default member 
group is called "_member_". Horizon is looking for a group called "Member". 

There is a parameter in horizon config file that if changed to "_member_" will 
fix the error your seeing. 

Now as to your question on who the bug should go to... I don't know. But if you 
confirm this is actually the issue here, maybe someone else on the list will 
know.

Good luck, hope this helps. 

John Edrington

Sent from my mobile device.

- Reply message -
From: "Kodiak Firesmith" 
To: 
Subject: [Openstack] Where should I report an issue w/ PackStack?
Date: Thu, Mar 27, 2014 8:59 PM
I'm having a hard time figuring out if this bug should go to the Packstack 
folks, the OpenStack folks, or the Redhat folks. I'm not totally sure it's a 
Packstack thing; that's just a hunch.

On a pristine RHEL 6.5 installation w/ Packstack Havana I noticed that any time 
you try to create a project or modify an existing one in the admin panel, you 
get a front-end error that maps to this traceback:

2014-03-28 00:57:22,014 23159 ERROR django.request Internal Server Error: 
/dashboard/admin/projects/8d0d79b82c1e42a8bcb07b3c2d4d4e29/update/Traceback 
(most recent call last):
  File "/usr/lib/python2.6/site-packages/django/core/handlers/base.py", line 
136, in get_response    response = response.render()  File 
"/usr/lib/python2.6/site-packages/django/template/response.py", line 104, in 
render
    self._set_content(self.rendered_content)  File 
"/usr/lib/python2.6/site-packages/django/template/response.py", line 81, in 
rendered_content    content = template.render(context)
  File "/usr/lib/python2.6/site-packages/django/template/base.py", line 140, in 
render    return self._render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 134, in _render
    return self.nodelist.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 823, in render 
   bit = self.render_node(node, context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 837, in 
render_node
    return node.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 478, in 
render    output = self.nodelist.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 823, in render
    bit = self.render_node(node, context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 837, in 
render_node    return node.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/loader_tags.py", line 53, in 
render
    result = self.nodelist.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 823, in render 
   bit = self.render_node(node, context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 837, in 
render_node
    return node.render(context)  File 
"/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 193, in 
render    nodelist.append(node.render(context))  File 
"/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 275, in 
render
    match = condition.eval(context)  File 
"/usr/lib/python2.6/site-packages/django/template/defaulttags.py", line 825, in 
eval    return self.value.resolve(context, ignore_failures=True)
  File "/usr/lib/python2.6/site-packages/django/template/base.py", line 571, in 
resolve    obj = self.var.resolve(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 721, in resolve
    value = self._resolve_lookup(context)  File 
"/usr/lib/python2.6/site-packages/django/template/base.py", line 772, in 
_resolve_lookup    current = current()  File 
"/usr/lib/python2.6/site-packages/horizon/workflows/base.py", line 451, in 
has_required_fields
    return any(field.required for field in self.action.fields.values())  File 
"/usr/lib/python2.6/site-packages/horizon/workflows/base.py", line 376, in 
action    context)  File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/projects/workflows.py",
 line 167, in __init__
    redirect=reverse(INDEX_URL))  File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/projects/workflows.py",
 line 163, in __init__
    raise exceptions.NotFound(msg)NotFound: Could not find default role 
"Member" in Keystone

I assume that a basic installation of Packstack on a pristine host should not 
be generating tracebacks when you attempt to do admin tasks in the project view 
as admin.

Any ideas whom I should file this bug with?
Thanks, - Kodiak Firesmith___
Mailing list: http:

Re: [Openstack] [ceilometer] how to list l3 meters using neutron meter-labels?

[Nejc Saje]

If I’m not mistaken, you should be able to get the relevant samples by 
filtering on resource_id being the label’s ID, e.g.

`ceilometer sample-list -q resource_id=`

Cheers,
Nejc

On Mar 28, 2014, at 11:40 AM, Kelam, Koteswara Rao  
wrote:

> Hi All,
>  
> I am using icehouse-2. In my setup 10.64.201.0/24 is external network and set 
> it as router gateway.
> |10.64.201.0/24|<--->|router|<-->|22.0.0.0/24|
>  
> Now I want see the rx and tx stats of qg-XX interface of router as meters.
> I configured neutron metering label and rule as follows.
> sdn@koteswar-ice-osc:~$ neutron meter-label-show INCOMING
> sdn@koteswar-ice-osc:~$ neutron meter-label-rule-create INCOMING 
> 10.64.201.0/24 --direction ingress
>  
> But I don’t know how to see the stats associated with label  INCOMING. After 
> creating label, how to see it as a meter in the collector side?
> “ceilometer meter-list/sample-list” not listing anything related to this 
> label. Please help.
>  
> Thanks in advance
> Koteswar
> ___
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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] [Ceilometer] Example "create alarm" via REST API

[Eoghan Glynn]

> Hello Eoghan,
> 
> Thanks for the steps..
> 
> when I launched my stack(autoscaling), Alarms are created but not generating,
> showing insufficient data. In the log I found below error
> 
> I have found something from my log .
> 
> ==> ceilometer-collector.log <==
>  2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] error calling
>  'port': 'tenant_id'
>  2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] 'tenant_id'
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension Traceback (most
>  recent call last):
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File
>  "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 145, in
>  _invoke_one_plugin
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension
>  response_callback(func(e, *args, **kwds))
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File
>  "/usr/lib/python2.7/dist-packages/ceilometer/collector/service.py", line
>  293, in _process_notification_for_ext
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension
>  p(list(ext.obj.to_samples(notification)))
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File
>  "/usr/lib/python2.7/dist-packages/ceilometer/network/notifications.py",
>  line 89, in process_notification
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension
>  project_id=message['payload']['tenant_id'],
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension KeyError: 'tenant_id'
>  2014-03-25 05:40:56.308 1047 TRACE stevedore.extension


What version are you using?

That's an issue with incoming neutron notification, shouldn't impact
on cpu_util gathering.

Do you have visibility on the stats related to the instance? e.g.

  $ ceilometer statistics -m cpu_util -q resource=$INSTANCE_ID

/Eoghan

 
> refer:
>  https://bugs.launchpad.net/ceilometer/+bug/1276761
> 
> I am not sure its a bug or I am doing something wrong ..?
> 
> Please let me know
> 
> -Original Message-
> From: Eoghan Glynn [mailto:egl...@redhat.com]
> Sent: Friday, March 28, 2014 3:31 PM
> To: Mark Vlcek (mavlcek)
> Cc: openstack
> Subject: Re: [Openstack] [Ceilometer] Example "create alarm" via REST API
> 
> 
> 
> > Hi All,
> >
> > Can somebody give me an example of how I’d create an alarm via the
> > Telemetry (aka Ceilometer) REST API? I can’t for the life of me find a
> > simple example online, say for example, how to set an alarm for when
> > cpu_util > 80% for a given running instance.
> 
> See this little RDO getting-started guide I wrote a while back:
> 
>   http://openstack.redhat.com/CeilometerQuickStart
> 
> there's an example therein of creating an alarm via the CLI:
> 
>   $ ceilometer alarm-threshold-create --name cpu_high --description 'instance
>   running hot'  \
>   --meter-name cpu_util  --threshold 70.0 --comparison-operator gt
>   --statistic avg \
>   --period 600 --evaluation-periods 3 \
>   --alarm-action 'log://' \
>   --query resource_id=INSTANCE_ID
> 
> Just modify the period, evaluation-periods, threshold to suit your use-case.
> 
> To see the actual JSON payload, simply use the --debug option:
> 
>   $ ceilometer --debug alarm-threshold-create ...
>   ...
>   curl -i -X POST -H 'X-Auth-Token: TOKEN' -H 'Content-Type:
>   application/json' -H 'Accept: application/json' -H 'User-Agent:
>   python-ceilometerclient' -d '{"alarm_actions": ["log://"], "description":
>   "instance running hot", "threshold_rule": {"meter_name": "cpu_util",
>   "evaluation_periods": 3, "period": 600, "statistic": "avg", "threshold":
>   70.0, "query": [{"field": "resource_id", "type": "", "value":
>   "INSTANCE_ID", "op": "eq"}], "comparison_operator": "gt"},
>   "repeat_actions": false, "type": "threshold", "name": "cpu_high"}'
>   http://IP_ADDR:8777/v2/alarms
> 
> You could also look at the official project API docco here:
> 
>   http://docs.openstack.org/developer/ceilometer/webapi/v2.html
> 
> Cheers,
> Eoghan
> 
> 
> >
> > I saw this example in a presentation somewhere, but it’s not exactly
> > self-explanatory.
> >
> > POST /v2/alarms
> >
> > {
> > "alarm_actions": [
> > "http://site:8000/alarm";
> > ],
> > "insufficient_data_actions": [
> > "http://site:8000/nodata";
> > ],
> > "ok_actions": [
> > "http://site:8000/ok";
> > ],
> > "comparison_operator": "gt",
> > "description": "An alarm",
> > "evaluation_periods": 2,
> > "matching_metadata": {
> > "key_name": "key_value"
> > },
> > "meter_name": "storage.objects",
> > "name": "SwiftObjectAlarm",
> > "period": 240,
> > "statistic": "avg",
> > "threshold": 200
> > }
> >
> > Thanks,
> > Mark
> >
> > ___
> > 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@lis

[Openstack] Virtual switch component with ports

[Shital Patil]

I want to make virtual switch configurations on openstack through java code
using library like Jclouds. There is no component for switch (while router
component is available and visible through horizon)

I read this-
http://docs.openstack.org/api/openstack-network/2.0/content/Ports.html
but still I am not clear about how I can do this.
Please provide suggestions

Thank you
___
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] [Ceilometer] Example "create alarm" via REST API

[Nejc Saje]

This bug is marked as fixed. Are you certain you have the latest version of 
Ceilometer?

Cheers,
Nejc

On Mar 28, 2014, at 11:50 AM, m.channappa.nega...@accenture.com wrote:

> Hello Eoghan,
> 
> Thanks for the steps..
> 
> when I launched my stack(autoscaling), Alarms are created but not generating, 
>  showing insufficient data. In the log I found below error
> 
> I have found something from my log .
> 
> ==> ceilometer-collector.log <==
> 2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] error calling 
> 'port': 'tenant_id'
> 2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] 'tenant_id'
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension Traceback (most recent 
> call last):
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
> "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 145, in 
> _invoke_one_plugin
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
> response_callback(func(e, *args, **kwds))
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
> "/usr/lib/python2.7/dist-packages/ceilometer/collector/service.py", line 293, 
> in _process_notification_for_ext
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
> p(list(ext.obj.to_samples(notification)))
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
> "/usr/lib/python2.7/dist-packages/ceilometer/network/notifications.py", line 
> 89, in process_notification
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
> project_id=message['payload']['tenant_id'],
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension KeyError: 'tenant_id'
> 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension
> 
> refer:
> https://bugs.launchpad.net/ceilometer/+bug/1276761
> 
> I am not sure its a bug or I am doing something wrong ..?
> 
> Please let me know
> 
> -Original Message-
> From: Eoghan Glynn [mailto:egl...@redhat.com]
> Sent: Friday, March 28, 2014 3:31 PM
> To: Mark Vlcek (mavlcek)
> Cc: openstack
> Subject: Re: [Openstack] [Ceilometer] Example "create alarm" via REST API
> 
> 
> 
>> Hi All,
>> 
>> Can somebody give me an example of how I’d create an alarm via the
>> Telemetry (aka Ceilometer) REST API? I can’t for the life of me find a
>> simple example online, say for example, how to set an alarm for when
>> cpu_util > 80% for a given running instance.
> 
> See this little RDO getting-started guide I wrote a while back:
> 
>  http://openstack.redhat.com/CeilometerQuickStart
> 
> there's an example therein of creating an alarm via the CLI:
> 
>  $ ceilometer alarm-threshold-create --name cpu_high --description 'instance 
> running hot'  \
>  --meter-name cpu_util  --threshold 70.0 --comparison-operator gt  
> --statistic avg \
>  --period 600 --evaluation-periods 3 \
>  --alarm-action 'log://' \
>  --query resource_id=INSTANCE_ID
> 
> Just modify the period, evaluation-periods, threshold to suit your use-case.
> 
> To see the actual JSON payload, simply use the --debug option:
> 
>  $ ceilometer --debug alarm-threshold-create ...
>  ...
>  curl -i -X POST -H 'X-Auth-Token: TOKEN' -H 'Content-Type: application/json' 
> -H 'Accept: application/json' -H 'User-Agent: python-ceilometerclient' -d 
> '{"alarm_actions": ["log://"], "description": "instance running hot", 
> "threshold_rule": {"meter_name": "cpu_util", "evaluation_periods": 3, 
> "period": 600, "statistic": "avg", "threshold": 70.0, "query": [{"field": 
> "resource_id", "type": "", "value": "INSTANCE_ID", "op": "eq"}], 
> "comparison_operator": "gt"}, "repeat_actions": false, "type": "threshold", 
> "name": "cpu_high"}' http://IP_ADDR:8777/v2/alarms
> 
> You could also look at the official project API docco here:
> 
>  http://docs.openstack.org/developer/ceilometer/webapi/v2.html
> 
> Cheers,
> Eoghan
> 
> 
>> 
>> I saw this example in a presentation somewhere, but it’s not exactly
>> self-explanatory.
>> 
>> POST /v2/alarms
>> 
>> {
>> "alarm_actions": [
>> "http://site:8000/alarm";
>> ],
>> "insufficient_data_actions": [
>> "http://site:8000/nodata";
>> ],
>> "ok_actions": [
>> "http://site:8000/ok";
>> ],
>> "comparison_operator": "gt",
>> "description": "An alarm",
>> "evaluation_periods": 2,
>> "matching_metadata": {
>> "key_name": "key_value"
>> },
>> "meter_name": "storage.objects",
>> "name": "SwiftObjectAlarm",
>> "period": 240,
>> "statistic": "avg",
>> "threshold": 200
>> }
>> 
>> Thanks,
>> Mark
>> 
>> ___
>> 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
> 
> 
> 
> This message is for the

Re: [Openstack] [Ceilometer] Example "create alarm" via REST API

[m.channappa.negalur]

Hello Eoghan,

Thanks for the steps..

when I launched my stack(autoscaling), Alarms are created but not generating,  
showing insufficient data. In the log I found below error

I have found something from my log .

==> ceilometer-collector.log <==
 2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] error calling 
'port': 'tenant_id'
 2014-03-25 05:40:56.308 1047 ERROR stevedore.extension [-] 'tenant_id'
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension Traceback (most recent 
call last):
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 145, in 
_invoke_one_plugin
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
response_callback(func(e, *args, **kwds))
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
"/usr/lib/python2.7/dist-packages/ceilometer/collector/service.py", line 293, 
in _process_notification_for_ext
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
p(list(ext.obj.to_samples(notification)))
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension File 
"/usr/lib/python2.7/dist-packages/ceilometer/network/notifications.py", line 
89, in process_notification
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension 
project_id=message['payload']['tenant_id'],
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension KeyError: 'tenant_id'
 2014-03-25 05:40:56.308 1047 TRACE stevedore.extension

refer:
 https://bugs.launchpad.net/ceilometer/+bug/1276761

I am not sure its a bug or I am doing something wrong ..?

Please let me know

-Original Message-
From: Eoghan Glynn [mailto:egl...@redhat.com]
Sent: Friday, March 28, 2014 3:31 PM
To: Mark Vlcek (mavlcek)
Cc: openstack
Subject: Re: [Openstack] [Ceilometer] Example "create alarm" via REST API



> Hi All,
>
> Can somebody give me an example of how I’d create an alarm via the
> Telemetry (aka Ceilometer) REST API? I can’t for the life of me find a
> simple example online, say for example, how to set an alarm for when
> cpu_util > 80% for a given running instance.

See this little RDO getting-started guide I wrote a while back:

  http://openstack.redhat.com/CeilometerQuickStart

there's an example therein of creating an alarm via the CLI:

  $ ceilometer alarm-threshold-create --name cpu_high --description 'instance 
running hot'  \
  --meter-name cpu_util  --threshold 70.0 --comparison-operator gt  
--statistic avg \
  --period 600 --evaluation-periods 3 \
  --alarm-action 'log://' \
  --query resource_id=INSTANCE_ID

Just modify the period, evaluation-periods, threshold to suit your use-case.

To see the actual JSON payload, simply use the --debug option:

  $ ceilometer --debug alarm-threshold-create ...
  ...
  curl -i -X POST -H 'X-Auth-Token: TOKEN' -H 'Content-Type: application/json' 
-H 'Accept: application/json' -H 'User-Agent: python-ceilometerclient' -d 
'{"alarm_actions": ["log://"], "description": "instance running hot", 
"threshold_rule": {"meter_name": "cpu_util", "evaluation_periods": 3, "period": 
600, "statistic": "avg", "threshold": 70.0, "query": [{"field": "resource_id", 
"type": "", "value": "INSTANCE_ID", "op": "eq"}], "comparison_operator": "gt"}, 
"repeat_actions": false, "type": "threshold", "name": "cpu_high"}' 
http://IP_ADDR:8777/v2/alarms

You could also look at the official project API docco here:

  http://docs.openstack.org/developer/ceilometer/webapi/v2.html

Cheers,
Eoghan


>
> I saw this example in a presentation somewhere, but it’s not exactly
> self-explanatory.
>
> POST /v2/alarms
>
> {
> "alarm_actions": [
> "http://site:8000/alarm";
> ],
> "insufficient_data_actions": [
> "http://site:8000/nodata";
> ],
> "ok_actions": [
> "http://site:8000/ok";
> ],
> "comparison_operator": "gt",
> "description": "An alarm",
> "evaluation_periods": 2,
> "matching_metadata": {
> "key_name": "key_value"
> },
> "meter_name": "storage.objects",
> "name": "SwiftObjectAlarm",
> "period": 240,
> "statistic": "avg",
> "threshold": 200
> }
>
> Thanks,
> Mark
>
> ___
> 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



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 

Re: [Openstack] [ceilometer] how to list l3 meters using neutron meter-labels?

[Kelam, Koteswara Rao]

Hi All,

I am using icehouse-2. In my setup 10.64.201.0/24 is external network and set 
it as router gateway.
|10.64.201.0/24|<--->|router|<-->|22.0.0.0/24|

Now I want see the rx and tx stats of qg-XX interface of router as meters.
I configured neutron metering label and rule as follows.
sdn@koteswar-ice-osc:~$ neutron meter-label-show INCOMING
sdn@koteswar-ice-osc:~$ neutron meter-label-rule-create INCOMING 10.64.201.0/24 
--direction ingress

But I don't know how to see the stats associated with label  INCOMING. After 
creating label, how to see it as a meter in the collector side?
"ceilometer meter-list/sample-list" not listing anything related to this label. 
Please help.

Thanks in advance
Koteswar
___
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] Live migration failing with Domain not found

[Nikola Pajtic]

Hi guys,

My colleague has asked the following question on ask.openstack.org:
https://ask.openstack.org/en/question/25962/why-is-live-migration-failing-with-domain-not-found/

Since he hasn't got any reply, he asked me to repeat the same question
here. In addition to his topic, just to add that we are using NFSv4
(rw,no_root_squash) as shared file system, and we also tried running
Qemu as root user (since we found a forum post in which someone
suggested that as a workaround). Still no luck.

Any ideas?

Thank you in advance!

--
Nikola Pajtic

___
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] [Ceilometer] Example "create alarm" via REST API

[Eoghan Glynn]

> Hi All,
> 
> Can somebody give me an example of how I’d create an alarm via the Telemetry
> (aka Ceilometer) REST API? I can’t for the life of me find a simple example
> online, say for example, how to set an alarm for when cpu_util > 80% for a
> given running instance.

See this little RDO getting-started guide I wrote a while back:

  http://openstack.redhat.com/CeilometerQuickStart

there's an example therein of creating an alarm via the CLI:

  $ ceilometer alarm-threshold-create --name cpu_high --description 'instance 
running hot'  \
  --meter-name cpu_util  --threshold 70.0 --comparison-operator gt  
--statistic avg \
  --period 600 --evaluation-periods 3 \
  --alarm-action 'log://' \
  --query resource_id=INSTANCE_ID

Just modify the period, evaluation-periods, threshold to suit your use-case.

To see the actual JSON payload, simply use the --debug option:

  $ ceilometer --debug alarm-threshold-create ...
  ...
  curl -i -X POST -H 'X-Auth-Token: TOKEN' -H 'Content-Type: application/json' 
-H 'Accept: application/json' -H 'User-Agent: python-ceilometerclient' -d 
'{"alarm_actions": ["log://"], "description": "instance running hot", 
"threshold_rule": {"meter_name": "cpu_util", "evaluation_periods": 3, "period": 
600, "statistic": "avg", "threshold": 70.0, "query": [{"field": "resource_id", 
"type": "", "value": "INSTANCE_ID", "op": "eq"}], "comparison_operator": "gt"}, 
"repeat_actions": false, "type": "threshold", "name": "cpu_high"}' 
http://IP_ADDR:8777/v2/alarms

You could also look at the official project API docco here:

  http://docs.openstack.org/developer/ceilometer/webapi/v2.html

Cheers,
Eoghan


> 
> I saw this example in a presentation somewhere, but it’s not exactly
> self-explanatory.
> 
> POST /v2/alarms
> 
> {
> "alarm_actions": [
> "http://site:8000/alarm";
> ],
> "insufficient_data_actions": [
> "http://site:8000/nodata";
> ],
> "ok_actions": [
> "http://site:8000/ok";
> ],
> "comparison_operator": "gt",
> "description": "An alarm",
> "evaluation_periods": 2,
> "matching_metadata": {
> "key_name": "key_value"
> },
> "meter_name": "storage.objects",
> "name": "SwiftObjectAlarm",
> "period": 240,
> "statistic": "avg",
> "threshold": 200
> }
> 
> Thanks,
> Mark
> 
> ___
> 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

Re: [Openstack] Pip Error In Swift Installation (Swift All in One tutorial for a single node)

[Christian Schwede]

I think you hit the bug reported in
https://bugs.launchpad.net/swift/+bug/1217288

A suggested workaround is to do a

sudo pip install -r requirements.txt

right before you run "python setup.py".

Which distribution and release are you using?



Am 28.03.14 09:56, schrieb Ashish Dobhal:
> Hello sir;
> After making the sudo pip install --upgrade I got the following error.
> 
> File "*/usr/lib/python2.7/distutils/cmd.py", line 59, in __init__
> raise TypeError, "dist must be a Distribution instance"
> TypeError: dist must be a Distribution instance*.
> 
> in the following step 
> *sudo python setup.py develop*
> 
> 
> Note:I did the pip update before my swift installation.Should I do the
> update just before the *sudo pip install -r
> swift/test-requirements.txt*_  command.*
> **
> 
> 
> On Wed, Mar 26, 2014 at 12:22 PM, Ashish Dobhal
> mailto:dobhalashish...@gmail.com>> wrote:
> 
> Thanks Sir,
> i also want to know when to make the update.Before the swift
> installation or before  running sudo pip install -r
> swift/test-requirements.txt*_  command.
> 
> 
> On Wed, Mar 26, 2014 at 12:47 PM, Christian Schwede
>  > wrote:
> 
> Hello,
> 
> looks like your pip version is to old. Try updating it with:
> 
> sudo pip install -U pip
> 
> This worked for me in the past.
> 
> Christian
> 
> Am 25.03.14 19:33, schrieb Ashish Dobhal:
> > Dear Sir/Maam;
> > I am following the swift all in one tutorial.
> > I got he following error while running
> > _*sudo pip install -r swift/test-requirements.txt*_  cmd_*
> >
> > *_
> > _*ERROR
> >
> > *_
> > *pkg_resources.VersionConflict: (pip 1.0
> > (/usr/lib/python2.7/dist-packages), Requirement.parse('pip>=1.4'))
> >
> > 
> > Command python setup.py egg_info failed with error code 1
> > Storing complete log in /home/yashika/.pip/pip.log*
> > Please Reply.
> > Thank You.
> >
> >
> > ___
> > 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

Re: [Openstack] Pip Error In Swift Installation (Swift All in One tutorial for a single node)

[Ashish Dobhal]

Hello sir;
After making the sudo pip install --upgrade I got the following error.

File "*/usr/lib/python2.7/distutils/cmd.py", line 59, in __init__
raise TypeError, "dist must be a Distribution instance"
TypeError: dist must be a Distribution instance*.

in the following step
*sudo python setup.py develop*


Note:I did the pip update before my swift installation.Should I do the
update just before the *sudo pip install -r swift/test-requirements.txt*_
 command.*


On Wed, Mar 26, 2014 at 12:22 PM, Ashish Dobhal
wrote:

> Thanks Sir,
> i also want to know when to make the update.Before the swift installation
> or before  running sudo pip install -r swift/test-requirements.txt*_
>  command.
>
>
> On Wed, Mar 26, 2014 at 12:47 PM, Christian Schwede <
> christian.schw...@enovance.com> wrote:
>
>> Hello,
>>
>> looks like your pip version is to old. Try updating it with:
>>
>> sudo pip install -U pip
>>
>> This worked for me in the past.
>>
>> Christian
>>
>> Am 25.03.14 19:33, schrieb Ashish Dobhal:
>> > Dear Sir/Maam;
>> > I am following the swift all in one tutorial.
>> > I got he following error while running
>> > _*sudo pip install -r swift/test-requirements.txt*_  cmd_*
>> >
>> > *_
>> > _*ERROR
>> >
>> > *_
>> > *pkg_resources.VersionConflict: (pip 1.0
>> > (/usr/lib/python2.7/dist-packages), Requirement.parse('pip>=1.4'))
>> >
>> > 
>> > Command python setup.py egg_info failed with error code 1
>> > Storing complete log in /home/yashika/.pip/pip.log*
>> > Please Reply.
>> > Thank You.
>> >
>> >
>> > ___
>> > 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