Please $subject.
--
Thanks..
Best Regards...
www.yasith.info
..යසිත්..:~
Yasith Tharindu / யசித்
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More h
Less fun guys. Here's what an upload to SID revealed (see below).
I'll conflict the 2 packages, I guess the issue is in Ubuntu as well.
Thomas
Original Message
Subject: Bug#631834: python-novaclient and simh: error when trying to
install together
Resent-Date: Mon, 27 Jun 2011 1
On 06/27/2011 11:29 PM, Martin Zobel-Helas wrote:
> Package: nova-common
> Version: 2011.2-1
> Severity: important
> Tags: patch
>
> Hi Thomas,
>
> i played around with nova i bit today, and found a small error, which
> took me a while to find:
>
> --- nova_sudoers2011-06-27 17:26:14.000
Thanks for your response, Brian and Jay!
Response inline..
> (There is a summary at the bottom!)
>
> Jay/Kei/Everyone,
>
> I thought the exact same thing but I had completely forgotten to respond.
>
> The term 'snapshot', as it is currently being used IMO is incorrect and/or
> misleading. Perh
The first step might be a well known (inside OpenStack) port for keystone and then register with IANA to avoid any conflicts. Second, the service should have a ping-pong interface, with pong sending a version number (to make it easy for clients to make sure they can find the functionalities they ar
We have the service catalog functionality in Keystone which provides
discovery.
We still need to complete the user story of how a service registers
itself; the functionality is available, but not fully documented as a
story.
The question of ports still remains, though. How do you find Keystone?
O
The effort Jay (and others) are doing on standardizing across services
could also be helpful here; having a -p --ports command-line and config
setting that works with all services would make it easier to stand up a
set of services on non-conflicting ports.
On 6/25/11 9:11 PM, "Todd Willey" wrote:
Hi Yuriy,
The project home is http://launchpad.net/keystone. On that page are links to
many of the discussions on the topic.
The code is available on the github repository mentioned there;
http://github.com/rackspace/keystone. There are also a number of issues listed
there which contain conver
?? wrote:
> hi,
> why was the feature of 'boot-from-volume' moved from d2 to d3?
I discussed with Isaku Yamahata and the feature will not be fully
delivered in time for diablo-2. There are three parts: one that is
already merged, one that should be merged (hopefully in time for
diablo-2, see
hi,
why was the feature of 'boot-from-volume' moved from d2 to d3?
At 2011-06-27 17:00:54，"Thierry Carrez" wrote:
>Hello everyone,
>
>Tomorrow morning we'll cut the release branch for Nova diablo-2, so we
>need to have the diablo-2 features merged before the end of today !
>
>So please spend some
Thank you for your fast reply! We are looking forward to this feature.
Regards, :),
At 2011-06-27 17:51:51，"Thierry Carrez" wrote:
>张俊峰 wrote:
>> hi,
>> why was the feature of 'boot-from-volume' moved from d2 to d3?
>
>I discussed with Isaku Yamahata and the feature will not be fully
>deliver
Hello everyone,
Tomorrow morning we'll cut the release branch for Nova diablo-2, so we
need to have the diablo-2 features merged before the end of today !
So please spend some time today reviewing diablo-2-targeted feature
branches. They are shown with a small hourglass icon at the end of the
lin
There is blueprint
https://blueprints.launchpad.net/keystone/+spec/pluggable-identity-store with
"Beta Available".
How can I put my hands on this beta? Where is this code? Are there any
design decisions made on this topic?
I'm specifically interested in LDAP storage backend.
Kind regards, Yuriy.
_
Todd Willey wrote:
> I think people will probably deploy in such a way that clients talk to
> 80 or 443. But there are a number of ways to get to that outcome,
> including specifying it in the server configuration, or running behind
> load balancers or other front-end services. Running everything
14 matches
Mail list logo
