Hi Salvatore!Welcome in the team :)
Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15
Le 28 janv. 2013 à 21:30, Anne Gentle a...@openstack.org a écrit :Hi all -Salvatore is going to be doing bug triaging for the Quantum API, so I'd like him to be able to work on bugs in the
Welcome ;)
On 29/01/13 07:33, Razique Mahroua wrote:
Hi Salvatore!
Welcome in the team :)
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com mailto:razique.mahr...@gmail.com
Tel : +33 9 72 37 94 15
Le 28 janv. 2013 à 21:30, Anne Gentle a...@openstack.org
hello everyone,
i'm wondering if there is any rest api for componnets' version info.
i read the http://api.openstack.org/api-ref.html and find:
1) keystone truly have a rest api for version info:
# curl http://127.0.0.1:5000/v2.0/
{version: {status: beta, updated: 2011-11-19T00:00:00Z,...
2) nova
I vaguely remember some chatter on the last summit about using something
other than passwords for user authentication in keystone. However,
looking at the sourcecode and blueprints I can't seem to find this
feature. I see a lot of encryption-based in tokens, but not between the
end-user and
On 28-01-2013 16:26, Trinath Somanchi wrote:
Hi Stackers-
I have newly installed openstack keystone, glance in my Ubuntu 12.04 system
When I add image to glance, I get this error.
root@NewFolsomController:~# glance add name=testImage is-public=true
container_format=bare
Hello,
I am new to openstack and I have accidently inserted wrong Ip addresses in
the Quantum script (
https://raw.github.com/EmilienM/openstack-folsom-guide/master/scripts/quantum-networking.sh)
in openstack folsom guide (
Hi Folks,
I'm trying to understand the configuration required to create a durable
notification queue for billing with RabbitMQ. As I understand it for messages
to be durable there need to be three things:
- The exchange has to be created as durable
- The queue needs to be
If you hit keystone's root endpoint you should also get a list of versions
in the response -- today that only includes /v2.0/
# curl http://127.0.0.1:5000/ http://127.0.0.1:5000/v2.0/
-Dolph
On Mon, Jan 28, 2013 at 3:07 AM, Ajiva Fan aji.zq...@gmail.com wrote:
hello everyone,
i'm
I have to install a devstack multinode using 3 nodes configured as follows:
1) Controller on Ubuntu 12.04 LTS
2) Node Compute on Ubuntu 12.04 LTS with KVM hypervisor
3) Node Compute on XenServer
While in first two points I am successful, the third point show me the
following error when i launch
Only password and token authentications are natively supported (by default)
at the moment. There are also signature-based authentication APIs like ec2
and s3 available as extensions. Other mechanisms such as two-way SSL and
external authentication via a web frontend is also possible?
In v3, we
Also, aren't the release names always *California* cities? Thereby Hillsboro,
Oregon isn't a valid choice...
- Gabriel
-Original Message-
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-
Also, aren't the release names always *California* cities?
Nope. =)
http://wiki.openstack.org/ReleaseNaming
At Your Service,
--
Mark T. Voelker
On 1/28/13 3:23 PM, Gabriel Hurley wrote:
Also, aren't the release names always *California* cities? Thereby Hillsboro,
Oregon isn't a valid
I stand corrected! Thanks. ;-)
- Gabriel
-Original Message-
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-
bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
Mark T. Voelker
Sent: Monday, January 28, 2013 1:18 PM
To:
Hi all,
I want to know if this bug has been fixed or not.
https://bugs.launchpad.net/nova/+bug/719798. When starting an instance, I
still get this error:
cloud-setup: checking
http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Network is
Hello folks,
I'm getting a problem, some days ago i've logged into dashboard with no
problems, but today, I've tried to log into dashboard and i got this
message:
An error occurred authenticating. Please try again later.
And, i can't found the services runnig using the ubuntu CLI, i've tried to
Does anyone on the list have a disk they'd recommend for OpenStack swift?
I am looking at hardware from Dell and HP, and I've found that the
disks they offer are very expensive. For instance, HP's 2TB disk has
a MSRP of over $500, while you can get a Western Digital 2TB 'Red'
disk for $127.
Is
Hi,
If you installed OpenStack from the repositories, then you have all the
init scripts as well. You can then use the following command :
$ service nova-X start (x being the name of the service)
$ service keystone start
Regards,
Razique
Le mardi 29 janvier 2013, Guilherme Souza a écrit :
Title: raring_grizzly_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/246/Project:raring_grizzly_quantum_trunkDate of build:Mon, 28 Jan 2013 04:01:11 -0500Build duration:8 min 53 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/554/Project:precise_grizzly_nova_trunkDate of build:Mon, 28 Jan 2013 08:31:10 -0500Build duration:11 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/555/Project:precise_grizzly_nova_trunkDate of build:Mon, 28 Jan 2013 09:01:16 -0500Build duration:12 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/556/Project:precise_grizzly_nova_trunkDate of build:Mon, 28 Jan 2013 10:09:31 -0500Build duration:9 min 41 secBuild cause:Started by user Chuck ShortBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/557/Project:precise_grizzly_nova_trunkDate of build:Mon, 28 Jan 2013 10:31:12 -0500Build duration:11 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/96/Project:precise_grizzly_keystone_trunkDate of build:Mon, 28 Jan 2013 12:01:09 -0500Build duration:22 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/558/Project:precise_grizzly_nova_trunkDate of build:Mon, 28 Jan 2013 12:02:12 -0500Build duration:17 minBuild cause:Started by an SCM changeBuilt
at 20130128
at 20130128
Title: precise_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/98/Project:precise_grizzly_keystone_trunkDate of build:Mon, 28 Jan 2013 14:01:09 -0500Build duration:40 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_keystone_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/99/Project:precise_grizzly_keystone_trunkDate of build:Mon, 28 Jan 2013 14:31:15 -0500Build duration:5 min 46 secBuild cause:Started by an SCM
See http://10.189.74.7:8080/job/folsom_coverage/396/
--
Started by command line by jenkins
Building on master in workspace
http://10.189.74.7:8080/job/folsom_coverage/ws/
No emails were triggered.
[workspace] $ /bin/bash -x
Title: precise_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-cinderclient_trunk/30/Project:precise_grizzly_python-cinderclient_trunkDate of build:Tue, 29 Jan 2013 01:31:08 -0500Build duration:2 min 19 secBuild
30 matches
Mail list logo
