[Openstack] heat CLI not working after modifying roles

[kevin parrikar]

i have a user whose role was "_member_ "later changed to "heat_stack_user"
and again changed to "_member_" but now the user is not able to do any heat
commands as it returns
"ERROR: You are not authorized to complete this action". for heat
stack-list and other heat commands but "nova list "is working fine

I tried adding user to admin role

keystone user-role-add --user=user10 --tenant=tenant9 --role=admin

where "user10"  is member of 2-3 tenants:

But its still the same even with admin role.So i suppose when i changed the
role something else  also changed which i am not able to figure out.Can
somebody help me in fixing this.
___
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] at an advanced Overcloud enviroment, sometimes keystone works, sometimes does not work

[Shinobu]

Is there any change between 1st time and 2nd one?

Shinobu

On Thu, Aug 27, 2015 at 1:23 PM, Pan, Fengyun 
wrote:

> Hello,
>
> When using following site to create an advanced Overcloud, I find that
> sometimes keystone works, sometimes does not work.
>
> https://repos.fedorapeople.org/repos/openstack-m/docs/master/advanced_deployment/advanced_deployment.html
>
>
> 
> $ source overcloudrc
> $ openstack-status
> == Nova services ==
> openstack-nova-api: active
> openstack-nova-cert:inactive  (disabled on boot)
> openstack-nova-compute: active
> openstack-nova-network: inactive  (disabled on boot)
> openstack-nova-scheduler:   active
> openstack-nova-conductor:   active
> == Glance services ==
> openstack-glance-api:   active
> openstack-glance-registry:  active
> == Keystone service ==
> openstack-keystone: active
> == Horizon service ==
> openstack-dashboard:active
> == neutron services ==
> neutron-server: active
> neutron-dhcp-agent: active
> neutron-l3-agent:   inactive  (disabled on boot)
> neutron-metadata-agent: inactive  (disabled on boot)
> neutron-openvswitch-agent:  active
> == Swift services ==
> openstack-swift-proxy:  active
> openstack-swift-account:active
> openstack-swift-container:  active
> openstack-swift-object: active
> == Ceilometer services ==
> openstack-ceilometer-api:   active
> openstack-ceilometer-central:   active
> openstack-ceilometer-compute:   inactive  (disabled on boot)
> openstack-ceilometer-collector: active
> openstack-ceilometer-alarm-notifier:active
> openstack-ceilometer-alarm-evaluator:   active
> openstack-ceilometer-notification:  active
> == Heat services ==
> openstack-heat-api: active
> openstack-heat-api-cfn: active
> openstack-heat-api-cloudwatch:  active
> openstack-heat-engine:  active
> == Support services ==
> libvirtd:   active
> openvswitch:active
> dbus:   active
> rabbitmq-server:active
> memcached:  active
> --
>
> But the first time:
> --
> $ source overcloudrc
> $ openstack user list
> Invalid OpenStack Identity credentials.
> -
>
> the second time:
> -
> $ openstack user list
> +--++
> | ID   | Name   |
> +--++
> | 0faeea08393e4a4db07c06dfbd3607db | cinderv2   |
> | 17b23141251f4c838f2125e47efe2745 | ceilometer |
> | 1e765d328ae34685b6024bbf1ea874d1 | nova   |
> | 2b2ca0f5803a4ac08c6dd788b55348e2 | glance |
> | af255c0288eb4ef3bb9db8b9f49bcab5 | heat   |
> | b955d565d0d34adcab4165ca6e8c336a | cinder |
> | baad3e14bc0d4e68aba0b328279fba43 | ec2|
> | c3ea813bbe0d4ac9932cb07a6ab86665 | swift  |
> | ce424df01e1146bb84e16681e4e51534 | neutron|
> | dfe4e66cfc2f46a4bd0d38f0bbea3b7a | admin  |
> +--++
> -
>
> Is it bug?
>
> ___
> 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
>



-- 
Email:
 shin...@linux.com
 ski...@redhat.com

Life with Distributed Computational System based on OpenSource

___
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] at an advanced Overcloud enviroment, sometimes keystone works, sometimes does not work

[Pan, Fengyun]

Hello,

When using following site to create an advanced Overcloud, I find that 
sometimes keystone works, sometimes does not work.
https://repos.fedorapeople.org/repos/openstack-m/docs/master/advanced_deployment/advanced_deployment.html



$ source overcloudrc 
$ openstack-status 
== Nova services ==
openstack-nova-api: active
openstack-nova-cert:inactive  (disabled on boot)
openstack-nova-compute: active
openstack-nova-network: inactive  (disabled on boot)
openstack-nova-scheduler:   active
openstack-nova-conductor:   active
== Glance services ==
openstack-glance-api:   active
openstack-glance-registry:  active
== Keystone service ==
openstack-keystone: active
== Horizon service ==
openstack-dashboard:active
== neutron services ==
neutron-server: active
neutron-dhcp-agent: active
neutron-l3-agent:   inactive  (disabled on boot)
neutron-metadata-agent: inactive  (disabled on boot)
neutron-openvswitch-agent:  active
== Swift services ==
openstack-swift-proxy:  active
openstack-swift-account:active
openstack-swift-container:  active
openstack-swift-object: active
== Ceilometer services ==
openstack-ceilometer-api:   active
openstack-ceilometer-central:   active
openstack-ceilometer-compute:   inactive  (disabled on boot)
openstack-ceilometer-collector: active
openstack-ceilometer-alarm-notifier:active
openstack-ceilometer-alarm-evaluator:   active
openstack-ceilometer-notification:  active
== Heat services ==
openstack-heat-api: active
openstack-heat-api-cfn: active
openstack-heat-api-cloudwatch:  active
openstack-heat-engine:  active
== Support services ==
libvirtd:   active
openvswitch:active
dbus:   active
rabbitmq-server:active
memcached:  active
--

But the first time:
--
$ source overcloudrc
$ openstack user list
Invalid OpenStack Identity credentials.
-

the second time:
-
$ openstack user list
+--++
| ID   | Name   |
+--++
| 0faeea08393e4a4db07c06dfbd3607db | cinderv2   |
| 17b23141251f4c838f2125e47efe2745 | ceilometer |
| 1e765d328ae34685b6024bbf1ea874d1 | nova   |
| 2b2ca0f5803a4ac08c6dd788b55348e2 | glance |
| af255c0288eb4ef3bb9db8b9f49bcab5 | heat   |
| b955d565d0d34adcab4165ca6e8c336a | cinder |
| baad3e14bc0d4e68aba0b328279fba43 | ec2|
| c3ea813bbe0d4ac9932cb07a6ab86665 | swift  |
| ce424df01e1146bb84e16681e4e51534 | neutron|
| dfe4e66cfc2f46a4bd0d38f0bbea3b7a | admin  |
+--++
-

Is it bug?

___
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][ironic] Unit of memory_mb

[Shinobu]

Hello,

When I ran the following:

openstack baremetal introspection bulk start

As a result value of memory_mb was:

 ...
 | properties | {u'memory_mb': u'512', ...
 ...

What I was expecting is:

 524288

Because the host have 512GiB RAM.

 cat /proc/meminfo
 MemTotal:   528070612 kB

Did anyone have same or similar experience?

I've check the following pythons, so far I could have not found out
anything.

 ./ironicclient/client.py
 ./ironicclient/common/i18n.py
 ./ironicclient/common/utils.py
 ./ironicclient/exc.py
 ./ironicclient/openstack/common/apiclient/exceptions.py
 ./ironicclient/openstack/common/_i18n.py
 ./ironicclient/osc/plugin.py
 ./ironicclient/osc/client.py
 ./ironicclient/v1/client.py
 ./ironicclient/common/http.py
 ./ironicclient/v1/chassis.py
 ./ironicclient/common/base.py
 ./ironicclient/openstack/common/apiclient/base.py
 ./ironicclient/v1/driver.py
 ./ironicclient/v1/node.py
 ./ironicclient/v1/port.py

If I've missed anything, please point out it to me.

 Shinobu

-- 
Email:
 shin...@linux.com
 ski...@redhat.com

 Life with Distributed Computational System based on OpenSource

___
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] test

[Shinobu]

ignore me

-- 
Email:
 shin...@linux.com
 ski...@redhat.com

 Life w/ Linux 
___
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] [Swift] Delete handling with md5 collisions

[Chow, Anthony T (Anthony)** CTR **]

Shri,

Will these 2 discussions help resolve your doubt? 

https://answers.launchpad.net/swift/+question/156307

http://stackoverflow.com/questions/28379809/how-are-hash-collisions-handled


Anthony.

-Original Message-
From: Shrinand Javadekar [mailto:shrin...@maginatics.com] 
Sent: Wednesday, August 26, 2015 1:37 PM
To: openstack@lists.openstack.org
Subject: [Openstack] [Swift] Delete handling with md5 collisions

Hi,

I have a question about how object deletes are handled with md5 collisions. I 
looked at the code and here's my understanding of how things will work.

If I have two objects that have the same md5 hash, they will go to the same 
hash directory. Say, they go to /srv/node/r1/object/1024/eef/deadbeef/t1.data 
and /srv/node/r1/object/1024/eef/deadbeef/t2.data.

Now, if I delete object t1, Swift will created a new file called t3.ts and put 
it in the hash directory.
/srv/node/r1/object/1024/eef/deadbeef/t3.ts.

When the replicator runs, it will delete all files with timestamp less than t3. 
So will it delete both t1 and t2?

Thanks in advance.
-Shri

___
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] [Swift] Delete handling with md5 collisions

[Shrinand Javadekar]

Actually, I'm confused now. I used to think that Swift does HTTP
deletes by synchronously truncating the object file and renaming it
with a .ts extension. But the currently code simply creates a new file
with the request timestamp and .ts extension.

On Wed, Aug 26, 2015 at 1:37 PM, Shrinand Javadekar
 wrote:
> Hi,
>
> I have a question about how object deletes are handled with md5
> collisions. I looked at the code and here's my understanding of how
> things will work.
>
> If I have two objects that have the same md5 hash, they will go to the
> same hash directory. Say, they go to
> /srv/node/r1/object/1024/eef/deadbeef/t1.data and
> /srv/node/r1/object/1024/eef/deadbeef/t2.data.
>
> Now, if I delete object t1, Swift will created a new file called t3.ts
> and put it in the hash directory.
> /srv/node/r1/object/1024/eef/deadbeef/t3.ts.
>
> When the replicator runs, it will delete all files with timestamp less
> than t3. So will it delete both t1 and t2?
>
> Thanks in advance.
> -Shri

___
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] [Swift] Delete handling with md5 collisions

[Samuel Merritt]

On 8/26/15 1:37 PM, Shrinand Javadekar wrote:

Hi,

I have a question about how object deletes are handled with md5
collisions. I looked at the code and here's my understanding of how
things will work.

If I have two objects that have the same md5 hash, they will go to the
same hash directory. Say, they go to
/srv/node/r1/object/1024/eef/deadbeef/t1.data and
/srv/node/r1/object/1024/eef/deadbeef/t2.data.


That's two objects whose *names* have the same MD5 hash. The objects' 
contents are irrelevant when determining placement.



Now, if I delete object t1, Swift will created a new file called t3.ts
and put it in the hash directory.
/srv/node/r1/object/1024/eef/deadbeef/t3.ts.

When the replicator runs, it will delete all files with timestamp less
than t3. So will it delete both t1 and t2?


Correct. Two objects whose names have the same MD5 hash are considered 
equivalent by Swift.


If I remember correctly, since MD5 has a 128-bit output, that means you 
have a 50% probability of having a collision once your cluster reaches 
2^64 objects.


___
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] [Swift] Delete handling with md5 collisions

[Shrinand Javadekar]

Hi,

I have a question about how object deletes are handled with md5
collisions. I looked at the code and here's my understanding of how
things will work.

If I have two objects that have the same md5 hash, they will go to the
same hash directory. Say, they go to
/srv/node/r1/object/1024/eef/deadbeef/t1.data and
/srv/node/r1/object/1024/eef/deadbeef/t2.data.

Now, if I delete object t1, Swift will created a new file called t3.ts
and put it in the hash directory.
/srv/node/r1/object/1024/eef/deadbeef/t3.ts.

When the replicator runs, it will delete all files with timestamp less
than t3. So will it delete both t1 and t2?

Thanks in advance.
-Shri

___
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] [OSSA 2015-016] Information leak via Swift tempurls (CVE-2015-5223)

[Tristan Cacqueray]

==
OSSA-2015-016: Information leak via Swift tempurls
==

:Date: August 26, 2015
:CVE: CVE-2015-5223


Affects
~~~
- Swift: versions through 2.3.0


Description
~~~
Richard Hawkins from Rackspace and Swift core reviewers reported a
vulnerability in Swift tempurls. When in possession of a tempurl key
authorized for PUT, a malicious actor may retrieve other objects in
the same Swift account (tenant). All Swift setups are affected.


Patches
~~~
- https://review.openstack.org/217253 (Juno)
- https://review.openstack.org/217254 (Kilo)
- https://review.openstack.org/217255 (Kilo)
- https://review.openstack.org/217259 (Liberty)
- https://review.openstack.org/217260 (Liberty)


Credits
~~~
- Richard Hawkins from Rackspace (CVE-2015-5223)
- Swift core reviewers from OpenStack (CVE-2015-5223)


References
~~
- https://launchpad.net/bugs/1453948
- https://launchpad.net/bugs/1449212
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5223


Notes
~
- This fix will be included in future 2014.2.4 (juno) and 2015.1.2 (kilo)
  releases.

--
Tristan Cacqueray
OpenStack Vulnerability Management Team



signature.asc
Description: OpenPGP digital signature
___
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] Schedule Live - Tokyo OpenStack Summit

[Kendall Waters]

Hi everyone,

The schedule for the upcoming OpenStack Summit in Tokyo 
 is now available! 

SCHEDULE: https://www.openstack.org/summit/tokyo-2015/schedule/ 


There are two views for the Summit schedule. The Main Conference view is what 
the vast majority of attendees should use. Active Technical Contributors and 
operators who contribute to the Mitaka release cycle should use the Design 
Summit + Main Conference view of the Summit schedule. 

MOBILE APP
In the coming weeks the schedule mobile app will also be available for 
download. We will notify the community at that time. If you attended the 
Vancouver Summit then you can simply update the same mobile app to use for the 
Tokyo Summit.  

SPEAKER NOTIFICATIONS
If you submitted a talk - check your email. Everyone who submitted a speaking 
proposal for the Summit will soon receive an email notification to let them 
know whether or not their talk is accepted. The email sent to selected speakers 
contains next steps and a Summit speaker registration code. Each speaker is 
responsible for registering themselves to attend the Summit. Please make sure 
your colleagues read the email and complete this step.

Contact sum...@openstack.org  with any questions.

We’ll see you in Tokyo in two months. 

Cheers,
Kendall

___
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] Nova boot from volume problem after Kilo upgrade

[Jonathan Proulx]

That looks like exactly the thing John thanks, not sure why I missed
it on my first look through
.

David those look like some excellent slides.  As an operations
community we should find a better way of pulling together upgrade
experiences and related bugs.  If I come up with anything clever I'll
post to operators list about it.

-Jon

On Wed, Aug 26, 2015 at 1:26 PM, John Griffith
 wrote:
>
> On Wed, Aug 26, 2015 at 10:59 AM, Jonathan Proulx  wrote:
>>
>> Error: Flavor's disk is too small for
>> requested image
>
>
> Without looking closely, wonder if this is what you're seeing:
>
> https://bugs.launchpad.net/nova/+bug/1457517

___
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] Nova boot from volume problem after Kilo upgrade

[John Griffith]

On Wed, Aug 26, 2015 at 10:59 AM, Jonathan Proulx  wrote:

> Error: Flavor's disk is too small for
> requested image
>

​Without looking closely, wonder if this is what you're seeing:

https://bugs.launchpad.net/nova/+bug/1457517
___
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] Nova boot from volume problem after Kilo upgrade

[David Medberry]

Seen similar issues.
There are some known glance issues and also so nova filter issues going on
by default.

I'd look at enabling "verbose=True" in Nova and seeing if you can get
closer to the truth of what's going on and then tail the nova logs. We've
put that down in our runbooks as a best practice for debugging this.

The slides on our talk have more info:
http://j.mp/oskilo_twc

and I'll be adding another today.

(Our issue was kind of around glance api v1 and v2 differences and missing
descriptions among other things. Other issues also plagued the upgrade.)

See slides 8&9 and 12 and probably soon a 13.

On Wed, Aug 26, 2015 at 10:59 AM, Jonathan Proulx  wrote:

> Hi All,
>
> Before I open a bug...
>
> after Kilo upgrade I get 'Error: Flavor's disk is too small for
> requested image' when trying to boot from cinder volumes that are
> larger than the image-type root volume.
>
> This is a severe issue for me.  Has anyone else seen/reported this (I
> didn't see it looking at the BTS but may have missed it)
>
> Anyone have a work around other than duplicating all my existing
> flavors with a root size of '0' which would be a mess and confuse the
> hell out of my users.
>
> -Jon
>
> ps. instance types are stupid & users should be able to specify
> resources (within bounds) anyway but that's a longer argument and much
> harder fix :)
>
> ___
> 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] Nova boot from volume problem after Kilo upgrade

[Jonathan Proulx]

Hi All,

Before I open a bug...

after Kilo upgrade I get 'Error: Flavor's disk is too small for
requested image' when trying to boot from cinder volumes that are
larger than the image-type root volume.

This is a severe issue for me.  Has anyone else seen/reported this (I
didn't see it looking at the BTS but may have missed it)

Anyone have a work around other than duplicating all my existing
flavors with a root size of '0' which would be a mess and confuse the
hell out of my users.

-Jon

ps. instance types are stupid & users should be able to specify
resources (within bounds) anyway but that's a longer argument and much
harder fix :)

___
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] [SPAM?] Re: KVM or Vagrant+VirtualBox for OpenStack test environment

[Jerry Zhao]

You can also check out http://github.com/openstack-dev/devstack-vagrant,

which is pretty straight forward. I have managed to make kvm work but 
haven't pushed it upstream, virtualbox works as is though.




On 08/25/2015 04:03 PM, Chow, Anthony T (Anthony)** CTR ** wrote:

Thiago,

Thanks.  I am using a Ubuntu 12.04 desktop.  Let me try this out.

Anthony.

-Original Message-
From: Martinx - ジェームズ [mailto:thiagocmarti...@gmail.com]
Sent: Tuesday, August 25, 2015 3:49 PM
To: Chow, Anthony T (Anthony)** CTR **
Cc: openstack@lists.openstack.org
Subject: [SPAM?] Re: [Openstack] KVM or Vagrant+VirtualBox for OpenStack test 
environment

Hello Anthony,

  I'm trying to deploy OpenStack with Ansible + Vagrant (Mac + VirtualBox), but 
it fails...

  There is only one BUG, from what I'm seeing, which is related to MySQL 
startup process (it does not come up correctly), I tried two different Ubuntu 
Trusty Vagrant-ready images but, none worked.

  Maybe you can help!   :-D

  Check it out:


  https://github.com/sandvine/os-ansible-deployment-lite


  Basically, you need to:


  cd ~
  git clone https://github.com/sandvine/os-ansible-deployment-lite
  cd ~/os-ansible-deployment-lite
  ./os-deploy-vagrant.sh


Best,
Thiago

On 19 August 2015 at 11:54, Chow, Anthony T (Anthony)** CTR ** 
 wrote:

I want to see how the OpenStack development communities setup the test 
environment.

It seems to me there are some cases that DevStack or PackStack cannot handle 
and we need to spin up a mini test environment.

Or should I take this question to the IRC on Freenode #openstack-dev?

Thanks for the comments,

Anthony.

___
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



___
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] Monitoring resources outside OpenStack

[Pradeep Sathasivam (CW)]

Thanks Shinobu. I still don’t understand how this resource will be managed as 
it is outside of openstack.

Regards,
Pradeep. S

From: Shinobu [mailto:shinobu...@gmail.com]
Sent: Tuesday, August 25, 2015 6:32 PM
To: Pradeep Sathasivam (CW)
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] [ceilometer] Monitoring resources outside OpenStack

Yes, it's possible using inspectors.
Shinobu

On Tue, Aug 25, 2015 at 7:53 PM, Pradeep Sathasivam (CW) 
mailto:psath...@brocade.com>> wrote:
Hi,

I am trying to use ceilometer to monitor a physical switch/router connected to 
a compute node. Is it possible to achieve using ceilometer pollster?

If yes, I have few questions.

1. From where do I get the resource ID for the device. (Since router/switch is 
outside of OpenStack)
2. I am planning to get the credentials of the device from ml2/neutron conf. 
Will it be possible to read the conf from ceilometer service.
3. To create a new metric is it enough to create entry in 
/etc/ceilometer/pipeline.yaml?

Regards,
Pradeep. S


___
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] RBAC Functionality in Keystone (Kilo)

[sachin trivedi]

Hi Experts,

I am trying to setup multi-tenancy where my requirement is to map user's
with specified regions.
Currently we have mapping Project + Customer. What I am trying to achieve
is  whenever I launch an instance it ask which region you want to launch
the resources and those resources should be restricted to that region only.

Regards,
Sachin
___
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] the stack of server_console.yaml can't show novnc console url

[Pan, Fengyun]

Hello, stevebaker.

I think there is a problem about the temple file which at following internal 
site.

https://github.com/openstack/heat-templates/blob/master/hot/server_console.yaml

When using the template file to create stack, I can’t get novnc console url:
-
$ heat output-show stack single_console_type
{
  "novnc": null,
  "get_attr": "server",
  "console_urls": null
}
-
But fix the sing_console.patch1, I can get novnc console url successfully.
-
$ heat output-show stack single_console_type
"http://X.X.X.X:6080/vnc_auto.html?token=8c488ba6-77e3-4912-87da-6809fc2fffe7";
--
“x.x.x.x” is ip.

fix the sing_console.patch2, I can get other console url successfully. Like 
xvpvnc:
--
$ heat output-show stack xvpvnc_console_url
"http://127.0.0.1:6081/console?token=428a781b-13ff-4744-adb6-ff6f4b051cc4";
--


Thanks.


sing_console.patch1
Description: sing_console.patch1


sing_console.patch2
Description: sing_console.patch2
___
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] [neutron][SR-IOV] deprecate agent_required option for SR-IOV mechanism driver

[Moshe Levi]

Hi all,

When SR-IOV introduce in Juno the SR-IOV Agent supported only link state change.
Some Intel cards don't support setting link state, so to
resolve it the  SR-IOV mechanism driver supports agent and agent less mode.
>From Liberty the SR-IOV agent brings more functionality like
qos and port security so we want to make the agent mandatory.

I have already talked to pczesno from Intel and got his approval in the pci 
meeting [1]

For this to happen commit [2] and [3] need to be approved.



If anyone objects to this change now is the time to speak.





[1] - 
http://eavesdrop.openstack.org/meetings/pci_passthrough/2015/pci_passthrough.2015-06-23-13.09.log.txt

[2] - sriov: update port state even if ip link fails - 
https://review.openstack.org/#/c/195060/

[3] - SR-IOV: deprecate agent_required option - 
https://review.openstack.org/#/c/214324/



Thanks,

Moshe Levi
___
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