On 05/02/2012 07:19 AM, Mark McLoughlin wrote:
> Hey,
>
> On Tue, 2012-05-01 at 23:05 +0200, Loic Dachary wrote:
>> On 05/01/2012 06:13 PM, Mark McLoughlin wrote:
>>> Hi Loic,
>>>
>>> On Mon, 2012-04-30 at 12:15 +0200, Loic Dachary wrote:
>>> - I agree that we don't want to go too far with aggreg
Essex was released with support for both types of configuration files,
flagfiles (using the --) and the .ini file style, being the
"nova.conf.sample" file included in nova upstream code using the .ini
format.
>From a deployer point of view, this can be really confusing since official
docs, use the
Hello guys,
i'm trying out some api calls using cURL. I noticed that there were several
functions added which require api extensions. I'd really like to use those,
but sadly the required extensions are not preinstalled and neither do I know
how to install them.
A GET to the root of the api
On 05/02/2012 07:39 AM, Mark McLoughlin wrote:
> On Tue, 2012-05-01 at 23:05 +0200, Loic Dachary wrote:
>> On 05/01/2012 06:13 PM, Mark McLoughlin wrote:
>>> Hi Loic,
>>>
>>> On Mon, 2012-04-30 at 12:15 +0200, Loic Dachary wrote:
>>>
To prepare for the next meeting ( thursday 3rd, may 2012
>>>
On Wed, 2012-05-02 at 10:08 +0200, Loic Dachary wrote:
> > My impression is that the notifications system is intended to cover
> all
> > billable usage in at least Nova and Glance.
> It's also my understanding. Regarding swift, how would you suggest we
> approach the problem ? I see two possible co
On 05/02/2012 08:32 AM, Ghe Rivero wrote:
> Essex was released with support for both types of configuration files,
> flagfiles (using the --) and the .ini file style, being the
> "nova.conf.sample" file included in nova upstream code using the .ini format.
>
> From a deployer point of view, thi
HI Edgar,
Thank's !
Yes,as you can read in the doc, it will evoluate in the future.
Maybe someone will do it before me, the documentation is under a free
license, so feel free to add some features !
Best regards
Le mardi 01 mai 2012 à 23:52 -0700, Edgar Magana (eperdomo) a écrit :
> Hi Em
Andrew Bogott wrote:
> As part of the plugin framework, I'm thinking about facilities for
> adding commands to the nova-rootwrap list without directly editing the
> code in nova-rootwrap. This is, naturally, super dangerous; I'm worried
> that I'm going to open a security hole big enough to pa
Hi,
the policy with other python-* clients is not to have a stable release
branch (at most, a 2012.1 tag). The idea behind it, it's that the client
doesn't need to care about which version is the cloud working, and make all
clients be backward compatible. I don't know it this is also the case f
Eric Windisch wrote:
> I'd really like to see this security mechanism overhauled. Rootwrap was
> an improvement over what was there before, however, I don't believe that
> rootwrap is a viable long-term solution as currently designed. Rootwrap
> has resulted in the use of potentially insecure shel
Dan Prince wrote:
>>> * Migrations added during Folsom release cycle could be compacted
>>> during "E" release cycle. TBD if/when we do the next compaction.
>>
>> An alternative idea would be to do the compaction *prior* to the
>> Folsom relase instead of after, so that the cleanest possible
>> m
Hello,
I've noticed a problem restarting some of swift services, and I don't
know if it's related to a local configuration or a more general problem.
Basically when I try to restart swift-object-server and the service is
busy (you can see the Send-Q has data according to netstat), it stops
but th
Adam Young wrote:
> Can we get this on the Agenda for todays meeting, take an informal
> poll, and formalize it? If So, I'll write it up and post on the wiki.
Sorry, I missed the thread. Next time you can just add the topic
directly on the wiki @ http://wiki.openstack.org/Meetings/ProjectMeetin
Andrew Hutchings wrote:
> This was all actually covered in the i18n talk at the developer's summit:
>
> http://etherpad.openstack.org/FolsomI18N
>
> The information in there says "mailing list says no, feedback from
> session says yes (especially requested by operators in china) - need a
> vote?
There was a swift talk at the design summit that is related to (a):
http://etherpad.openstack.org/FolsomSwiftStatsd.
There is a good summary in the referenced blog post:
http://www.swiftstack.com/blog/2012/04/11/swift-monitoring-with-statsd/
-David
On 5/2/2012 4:19 AM, Mark McLoughlin wrote:
Dan Wendlandt wrote:
> Looks like that branch was never updated from milestone-proposed for
> Essex-RC2 to essex final. I'll take a look into why. In the mean time,
> you can just use the milestone-proposed
> tag:
> https://github.com/openstack/python-quantumclient/commits/milestone-proposed
Yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [cloud-devel] Bash Completion Scripts
Date: Wed, 02 May 2012 13:01:14 +0200
From: Dominik Heidler
Hi,
I've pushed the bash completion scripts for glance, keystone,
nova-manage and nova to github:
https:
By default sounds fine to me as long as there is a banner printed when
entering interactive mode which explains how to get help and (directly
and/or via the help) how to quit.
Doug Hellmann (doug.hellm...@dreamhost.com) wrote:
> I thought having it run like that by default made sense, but if the l
I recently submitted a few fixes to the test suite in various components
of openstack. These fixes are being merged in master, but the code
remains broken in the stable/essex branch. Review requests for
stable/essex either get rejected or stuck in limbo because it seems that
people don't know wh
This is really useful.
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Bernhard M. Wiedemann
Sent: Wednesday, May 02, 2012 5:56 PM
To: openstack@lists.launchpad.net
I disagree with all three... the line between "admin" and "not admin" is
going to get very blurry in the long run. Example: I may be a regular user,
but I've been granted what is "normally" an admin capability on tenant X.
Does that make me an admin? Do I now need to use two different clients?
I a
Until you do, getting clearer licensing on them would be a plus.
Read *everything* under "If your'e a developer"
http://wiki.openstack.org/HowToContribute
Add a blueprint or bug, submit a patch through gerrit. (Also, I say it belongs
in contrib)
Gerrit info:
http://wiki.openstack.org/GerritWo
Sweet :)thanks Dominik
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 2 mai 2012 à 15:01, Vaze, Mandar a écrit :This is really useful.-Original Message-From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.lau
(Apologies if this has been already answered in the mailing list, dealing with
a large backlog of mailing list emails).
With the current "nova" client (python-novaclient), there are Python bindings
so you can write Python scripts that use the API without having to deal with
the REST interface d
Dean Troyer (dtro...@gmail.com) wrote:
> On Tue, May 1, 2012 at 1:49 PM, Adam Spiers wrote:
> > Sorry, that made me think of another newbie question - is the
> > intention that all actions (including user- / site- / vendor-specific
> > extensions) *must* be implemented in Python using the client A
Correct.
Vish
On May 1, 2012, at 3:01 PM, Lillie Ross-CDSR11 wrote:
> Once again, I think I'm answering my own question.
>
> Nova_volume works in conjunction with nova-api to talk to any number of iscsi
> targets that you might have configured in your cloud. Each target runs an
> instance of
Doug Hellmann (doug.hellm...@dreamhost.com) wrote:
> I have started creating blueprints from my notes about activities we need
> to complete for the unified CLI. Please check the list at
> https://blueprints.launchpad.net/python-openstackclient/
Cool. Presumably we don't need to wait until the ne
Dean Troyer (dtro...@gmail.com) wrote:
> On Tue, May 1, 2012 at 12:54 PM, Adam Spiers wrote:
> > Agreed - while server-side auditing is a more important component than
> > client-side, having both sounds potentially useful to me too. And
> > while it's outside the scope of a CLI HIG discussion, i
going into interactive mode when no args are specified works well for virsh.
Vish
On May 1, 2012, at 8:08 PM, Doug Hellmann wrote:
> I thought having it run like that by default made sense, but if the list
> agrees we want a flag I'm happy to change it.
>
> On Tue, May 1, 2012 at 8:06 PM, Matt
Actually this ties into a thought I was having this morning.
How do we handle API versioning? I mean I would assume that we'd want
to poll the API server and see which versions are available and offer
command sets that are relevant. Silencing API version specific
commands that are not available
There has been a little more activity in the discussion in
http://etherpad.openstack.org/FolsumCLI this week regarding the name
of the python-openstackclient binary. It is currently 'stack'.
Summary of the vote as of now:
openstack: net +2
stack: net +1
ost: net 0
fog: net -1
oscli: -3
I have pr
Hey guys,
I'm playing aroung with the openstack api and I'm trying to change the
flavor of an instance. Thanks to the documentation I found the necessary
information to write the api call, which was done pretty fast and easy.
Sadly the api call has a secondary effect because after the execution
On Wed, May 2, 2012 at 9:13 AM, Lorin Hochstein
wrote:
> Will the new unified CLI also provide Python bindings, so people can write
> Python scripts against the libraries that ship with the CLI (like
> python-novaclient)? Or is that out of scope?
We use the existing API libraries from python-*cli
I don't think any clients truly implement this behavior *yet*, but each
service should return a multiple choice response (e.g.
http://keystone.openstack.org/api_curl_examples.html#id2 ) containing links
to each API version (/v1, /v2, /v3), and their status (e.g. deprecated,
current, beta, etc). Ide
Hi all -
I've written down the steps I've discovered while doing the Essex branch
for the docs:
http://wiki.openstack.org/Documentation/Release
Please review and let me know if you have questions.
Thanks to the CI team (James Blair rocks!) for the assistance in creating
parameters so that this p
On Wed, May 2, 2012 at 10:39 AM, Adam Spiers wrote:
> Doug Hellmann (doug.hellm...@dreamhost.com) wrote:
> > I have started creating blueprints from my notes about activities we need
> > to complete for the unified CLI. Please check the list at
> > https://blueprints.launchpad.net/python-openstac
The OpenStack QA Team holds public weekly meetings in
#openstack-meeting, Thursday at 13:00 EST (17:00 UTC). Everyone
interested in testing, quality assurance, performance engineering, etc,
should attend!
Agenda for next meeting
* Review of last week's action items
(jaypipes) Get dev-gat
Thanks for the information.
Edgar
-Original Message-
From: openstack-bounces+eperdomo=cisco@lists.launchpad.net
[mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On
Behalf Of Thierry Carrez
Sent: Wednesday, May 02, 2012 5:15 AM
To: openstack@lists.launchpad.net
Subject
On Wed, May 2, 2012 at 10:40 AM, Adam Spiers wrote:
> Dean Troyer (dtro...@gmail.com) wrote:
> > On Tue, May 1, 2012 at 12:54 PM, Adam Spiers wrote:
> > > Agreed - while server-side auditing is a more important component than
> > > client-side, having both sounds potentially useful to me too. A
On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein
wrote:
> (Apologies if this has been already answered in the mailing list, dealing
> with a large backlog of mailing list emails).
>
> With the current "nova" client (python-novaclient), there are Python
> bindings so you can write Python scripts th
Hi Lucio,
This should be all documented here:
http://keystone.openstack.org/configuringservices.html#configuring-swift-to-use-keystone
Chmouel
On Mon, Apr 30, 2012 at 3:26 PM, Lucio Cossio wrote:
> I'm still having problems to configure Swift with Keystone, someone can show
> me a proxy-serve
Also, I forgot to also mention that the Quantum guides will move from
/incubation to /trunk. I'll do a redirect on the server-side for these URLs:
http://docs.openstack.org/incubation/openstack-network/developer/quantum-api-1.0/content/
http://docs.openstack.org/incubation/openstack-network/admin
Ying Chun Guo wrote:
> Thank you for your comments. I'm glad to know that you are working for a
> larger "goal". I don't know
> Launchpad is broken with code strings now. What do you mean when you
> said "Launchpad to be
> broken with code strings now "?
Actually it's our tooling around that (and
Here's a little diagram I did up this morning for the required vm_state /
task_state transitions for compute api operations.
http://dl.dropbox.com/u/166877/PowerStates.pdf
Might be useful to the orchestration effort (or debugging in general)
Cheers,
Sandy
_
Oops, I saw the code change before this message and I went ahead and
approved it.
On Wed, May 2, 2012 at 10:59 AM, Dean Troyer wrote:
> There has been a little more activity in the discussion in
> http://etherpad.openstack.org/FolsumCLI this week regarding the name
> of the python-openstackclien
On Wed, May 2, 2012 at 10:18 AM, Doug Hellmann
wrote:
> Maybe I'm doing this wrong. I wanted to make a list of the things I know we
> have to do, so people who don't have access to the inside of my head can
> divy up the list (that's a short list). These things are "features" not
> "bugs" so I tho
You must not have allow_resize_to_same_host set in nova.conf.
On 5/2/2012 11:02 AM, Nicolas Odermatt wrote:
Hey guys,
I'm playing aroung with the openstack api and I'm trying to change the
flavor of an instance. Thanks to the documentation I found the
necessary information to write the api c
Dean Troyer (dtro...@gmail.com) wrote:
> On Tue, May 1, 2012 at 2:11 PM, Adam Spiers wrote:
> > As of my recent patch, --help is contextual in nova:
>
> I hadn't seen that yet...
>
> > and I have started work on some of the other commands too, so it would
> > be helpful if we could reach a conse
On Tue, May 1, 2012 at 7:55 PM, Doug Hellmann
wrote:
> There are a couple of ways to handle that:
>
> 1. A separate "openstackadmin" CLI that looks for commands using a different
> plugin namespace, and therefore only loads the admin commands.
>
> 2. Prefix admin-related commands in the unified cl
You make some fair points.
But consider the large class of cloud users that will never need to
bring up OpenStack from scratch, but rather maintain them. These users
will need to be able to easily identify the commands that pertain to
their daily maintenance, troubleshooting, and reporting tasks.
On May 2, 2012, at 11:30 AM, Doug Hellmann wrote:
>
>
> On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein
> wrote:
> (Apologies if this has been already answered in the mailing list, dealing
> with a large backlog of mailing list emails).
>
> With the current "nova" client (python-novaclient
Hi Mike,
I really need to bind loopback IP on my environment, I use the command
"ebtables -t nat -F" will flush the ebtables rule, so I can bind any IP I
wish,
but if I do stop libvirt-bin and start libvir-bin, the security rules will
be applied again,
if I remark no-ip-spoofing & no-arp-spoofing
I disagree pretty strongly with the idea of an admin binary.
Fundamentally my consternation with the idea comes from what I see as
such a clear and final delineation in what I expect will be a very
complex ACL set in the future. I can't see there being something as
simple as an admin and a user in
Hi all,
I was just looking over the efficient metering stuff yesterday.
Just a couple of questions, that might be dups (sorry if they are).
I am noticing that there seems to be a mix of billing specifics there and
metering specifics there.
If say metering can just provide as much raw data as p
Whatever. stack.sh is a conflict. So probably better.
On May 2, 2012 11:20 AM, "Doug Hellmann"
wrote:
> Oops, I saw the code change before this message and I went ahead and
> approved it.
>
> On Wed, May 2, 2012 at 10:59 AM, Dean Troyer wrote:
>
>> There has been a little more activity in the
With diablo plus some of our own changes, we've discovered our compute
nodes in some of our test nova environments are littered with
orphaned /dev/mapper/nbd* links to /dev/dm-* devices that are holding
the respective nbd devices. Of course, this causes injection failure
for VMs that attempt to re
+1 From me!
On Apr 28, 2012, at 11:41 PM, Mark McLoughlin wrote:
> Definite +1
>
> Mark.
>
> On Fri, 2012-04-27 at 11:09 -0400, Dan Prince wrote:
>> Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the
>> Nova security team. He has been helping chipping away at reviews
On Wed, May 2, 2012 at 1:56 PM, Matt Joyce wrote:
> I disagree pretty strongly with the idea of an admin binary.
I think many of us do; I (and I believe Doug) were simply preferring
1) a single binary with 2) division of commands.
> Fundamentally my consternation with the idea comes from what I
Good to have options.
On Wed, May 2, 2012 at 11:46 AM, Duncan McGreggor wrote:
> On Wed, May 2, 2012 at 1:56 PM, Matt Joyce wrote:
>> I disagree pretty strongly with the idea of an admin binary.
>
> I think many of us do; I (and I believe Doug) were simply preferring
> 1) a single binary with 2)
I skipped out on blue printing and just submitted a gerrit review for
adding argparse flags for specifying URL for specific APIs.
Is that cool or do we want blue prints at that level of low complexity?
-Matt
On Wed, May 2, 2012 at 10:13 AM, Dean Troyer wrote:
> On Wed, May 2, 2012 at 10:18 AM,
Hi Anne,
That sounds great! I would like to try out Essex on RHEL6, and wondering
if the EL6 repo and doc are ready for that?
Thanks,
Xin
On 5/2/2012 11:16 AM, Anne Gentle wrote:
Hi all -
I've written down the steps I've discovered while doing the Essex
branch for the docs:
http://wiki.op
On Wed, May 2, 2012 at 1:51 PM, Matt Joyce wrote:
> I skipped out on blue printing and just submitted a gerrit review for
> adding argparse flags for specifying URL for specific APIs.
Why is this needed? These URLs come from the service catalog. Cases
where you do need to override that use --os
Hi all,
I am making a y! specific backing store for glance and I was wondering if its
really necessary to modify the following file to ensure that the code for that
new store gets pulled in (or maybe I'm just doing it wrong).
diff --git a/glance/api/v1/images.py b/glance/api/v1/images.py
index
>> I skipped out on blue printing and just submitted a gerrit review for
>> adding argparse flags for specifying URL for specific APIs.
>
> Why is this needed? These URLs come from the service catalog. Cases
> where you do need to override that use --os-url as part of token flow
> auth, skipping
- Original Message -
> From: "Vishvananda Ishaya"
> To: "Dan Prince"
> Cc: openstack@lists.launchpad.net
> Sent: Thursday, April 26, 2012 4:14:25 PM
> Subject: Re: [Openstack] database migration cleanup
>
> +1. Might be nice to have some kind of test to verify that the new
> migration
Hi,
In Diablo was:
GET /users/{user_id}/roleRefs
In Essex it is maintained for compatibility reasons. I understand that this
is the obsolete now.
I can find:
PUT & DELETE /users/{user_id}/roles/OS-KSADM/{role_id}
How can get all the roles having a user_id?
GET /users/{user_id}/roles (i can't
cc'ing openstack list
On Wed, May 2, 2012 at 4:45 PM, Richard Raseley wrote:
> I am trying to figure out the best way to see view the distribution of a
> file or files across my test swift setup. I want to basically upload a file
> or files to containers and then be able to run a command or scrip
cc'ing openstack list
On Wed, May 2, 2012 at 4:08 PM, Randy Katz wrote:
> Hi,
>
> I am following this wonderful doc:
>
> http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL#Launch_an_Instance
>
> When I launch an image the vm status is error and the image seems to be
> running in an
cc'ing openstack list
On Wed, May 2, 2012 at 3:33 PM, Igor Laskovy wrote:
> Privet all from sunny Kiev!
>
> I have playing with Quantum with Quantum Linux Bridge plugin on Ubuntu
> 12.04 and have installed these packages:
>
> i quantum-server
> i quantum-plugin-linuxbridge-agent
> i A quantum
That seems like a reasonable approach. Would be nice to work with packagers to
verify that the packages are properly installing nbd. I'm pretty sure i used
kpartx because i didn't know about the max_part parameter.
Vish
On May 2, 2012, at 11:37 AM, Lee Schermerhorn wrote:
> With diablo plus
Hi Xinm
Have a look at
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL
cheers, Jan
On 05/02/2012 09:03 PM, Xin Zhao wrote:
Hi Anne,
That sounds great! I would like to try out Essex on RHEL6, and wondering
if the EL6 repo and doc are ready for that?
Thanks,
Xin
On 5
On Wed, May 2, 2012 at 2:46 PM, Duncan McGreggor wrote:
> On Wed, May 2, 2012 at 1:56 PM, Matt Joyce wrote:
> > I disagree pretty strongly with the idea of an admin binary.
>
> I think many of us do; I (and I believe Doug) were simply preferring
> 1) a single binary with 2) division of commands.
On Wed, May 2, 2012 at 1:23 PM, Adam Spiers wrote:
> Dean Troyer (dtro...@gmail.com) wrote:
> > On Tue, May 1, 2012 at 2:11 PM, Adam Spiers wrote:
> > > As of my recent patch, --help is contextual in nova:
> >
> > I hadn't seen that yet...
> >
> > > and I have started work on some of the other c
On Wed, May 2, 2012 at 6:01 PM, Doug Hellmann
wrote:
>
>
> On Wed, May 2, 2012 at 1:23 PM, Adam Spiers wrote:
>
>> Dean Troyer (dtro...@gmail.com) wrote:
>> > On Tue, May 1, 2012 at 2:11 PM, Adam Spiers wrote:
>> > > As of my recent patch, --help is contextual in nova:
>> >
>> > I hadn't seen th
On Wed, May 2, 2012 at 1:34 PM, Lorin Hochstein wrote:
>
> On May 2, 2012, at 11:30 AM, Doug Hellmann wrote:
>
>
>
> On Wed, May 2, 2012 at 10:13 AM, Lorin Hochstein > wrote:
>
>> (Apologies if this has been already answered in the mailing list, dealing
>> with a large backlog of mailing list ema
It seems change https://review.openstack.org/#/c/6569/ can help. Please see how it add a new configuration item to remove some filters.-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Mike Scherbakov From: Jimmy Tsai Sent by: openstack-bounces+gongysh=cn.ibm@lists.l
This is what i get.
1 > GET
http://192.168.1.41:35357/v2.0/users/ef1e63df85b641d7bf3c575bb8670cef/roles
1 > X-Auth-Token: secret0
2012-05-03 00:03:55,337 [http-bio-8080-exec-10] INFO api.identity - 2 *
LoggingFilter - Response received on thread http-bio-8080-exec-10
2 < 500
2 < Connection: clo
On Wed, May 2, 2012 at 2:31 PM, Joshua Harlow wrote:
> Hi all,
>
> I was just looking over the efficient metering stuff yesterday.
>
> Just a couple of questions, that might be dups (sorry if they are).
>
> I am noticing that there seems to be a mix of billing specifics there and
> metering speci
On your proxy server, use swift-get-nodes to see which servers your object is
on. With no arguments or --help you will get usage info.
--John
On May 2, 2012, at 3:48 PM, Duncan McGreggor wrote:
> cc'ing openstack list
>
> On Wed, May 2, 2012 at 4:45 PM, Richard Raseley wrote:
>> I am trying
Jay might have a better answer, but as far as I know, yes. You could probably
make the images stores truly pluggable (i.e. not needing to explicitly list
them out) without much work.
Brian
On May 2, 2012, at 12:23 PM, Joshua Harlow wrote:
> Hi all,
>
> I am making a y! specific backing store
Right, if there isn't that existing, then I think I might just make a blueprint
out of that. I just wanted to check beforehand that I am doing this right, or
if it already exists and I did it wrong...
Thx :-)
On 5/2/12 3:57 PM, "Brian Waldon" wrote:
Jay might have a better answer, but as far
Agree with your comments,
1. Metering tasks for me are mainly 2:
a) Collect relevant data
b) Correlate events (that's which "end event" corresponds with which "event
start") this is very important,
since only openstack knows how to correlate, but the billing system
2. Mediation process should ex
I just upload a video that shows the way i manage the billing described in
my previous mail in order to clarify:
http://youtu.be/3A1SdZS9Iak
Data is gathered and correlated in a own metering agent that i want to
conform with the ceilometer spec.
Data is submited to the billing system.
The billin
Hi.
I'd be interested in hearing from people who have implemented some form
of replication with glance. I'm especially interested in how you went
about it. I attended the session at the dev summit, but that was forward
looking, and I am pretty sure that there wasn't any mention of current
implemen
>
>
> It would be better if all OpenStack core components agreed on unified
> interfaces / messages for metering that would be easy to harvest without
> installing agents on nodes. This is also true for many services outside of
> the OpenStack eco-system. However, much in the same way munin and nag
Hi all,
I was thinking today about how nova-compute could become more pluggable.
I was wondering if there had been any thought into how say each method, say in
the compute-manager could almost become a set of stages in a pipeline.
For example the run instance method is really doing the following
I'm having some trouble using the Keystone API.
When I run
keystone --os_username=admin --os_password=password --os_auth_url=
http://192.168.1.50:5000/v2.0/ service-list
I get the following:
No handlers could be found for logger "keystoneclient.v2_0.client"
Unable to communicate with identity s
On 05/03/2012 12:06 AM, Luis Gervaso wrote:
This is what i get.
1 > GET
http://192.168.1.41:35357/v2.0/users/ef1e63df85b641d7bf3c575bb8670cef/roles
1 > X-Auth-Token: secret0
2012-05-03 00:03:55,337 [http-bio-8080-exec-10] INFO api.identity -
2 * LoggingFilter - Response received on thread
88 matches
Mail list logo
