Reposting here since this is mostly user related.
Original Message
Subject:[openstack-dev] [Heat] Running latest Heat against older
OpenStacks
Date: Wed, 22 May 2013 14:46:19 +1200
From: Steve Baker
Reply-To: OpenStack Development Mailing List
To: opensta
HI ,
i waited for more than 24 hrs after creating the instance but still
the instance shows as 'BUILDING' , i think the instance is stuck some where
while running
how can i debug the instance to know wt exactly is the problem ?
On Tue, Apr 16, 2013 at 2:19 PM, Razique Mahroua
wrot
Hi Deepak, that means the instance is not yet totally started, it is still building (meaning the base files being sent to the compute node roughly)You need to wait a bit for it to become "active"Regards,
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15
Le 16 avr. 2013 à
ive'.
2013-04-16
Wangpan
发件人:Deepak A.P
发送时间:2013-04-16 16:38
主题:[Openstack] Fwd: [openStack] deleting instances
收件人:"OpenStack Mailing List"
抄送:
Hi
I tried rebooting the instance got the below error
nova reboot
"ERROR: Cannot 'reboot' while
Hi
I tried rebooting the instance got the below error
nova reboot
"ERROR: Cannot 'reboot' while instance is in vm_state building (HTTP
409) (Request-ID: req-f83dab03-9db0-4cec )"
what could be issue ?
-- Forwarded message --
From: Deepak A.P
Date: Fri, Apr 5, 2013 at
Hello folks
can anybody help the Foundation staffing a booth at Open Compute Project
Summit January 16-17 2013, at the Santa Clara
Convention Center in California? Please contact Kathy (email below).
Cheers,
stef
Original Message
Subject:[openstack-community] Reques
Hi,
It should be available this week.
Regards
chuck
On 12-12-03 01:34 AM, Sina Sadeghi wrote:
Hello list,
When will this update be available tousers of the Ubuntu Cloud Archive?
Original Message
Subject: [openstack-announce] [ANNOUNCE] OpenStack Nova, Glance,
Keystone, C
Hello list,
When will this update be available tousers of the Ubuntu Cloud Archive?
Original Message
Subject: [openstack-announce] [ANNOUNCE] OpenStack Nova, Glance,
Keystone, Cinder, Quantum and Horizon 2012.2.1 released
Date: Thu, 29 Nov 2012 23:16:52 +
From: Mark
I did try that with no joy..
On 31 October 2012 15:50, Gui Maluf wrote:
> have you tried to disable vnc and check if is working?
>
> I followed official doc using multi_host. This is my vnc configs
>
> #VNC CONSOLE
> --vnc_enabled=true
> --vncproxy_url=http://cloud-controller-ip:6080
> --vnc_co
nova-manage service list showed all smiley faces, with the relevant service
running on the correct servers.
I've decided to not split it out now. I'm going to use what was the
controller just as an iscsi target, then run the full stack on what was
going to be the compute nodes.
Thanks for all you
And - what does `nova-manage service list` show.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 3:56 PM, "Kiall Mac Innes" wrote:
>
> Is libvirt actually running?
>
> Does `virsh list` exit with an error?
>
> Doesn't sounds VNC related to me.
>
> Thanks,
> Kiall
>
> Sent from my phone.
>
> On
Is libvirt actually running?
Does `virsh list` exit with an error?
Doesn't sounds VNC related to me.
Thanks,
Kiall
Sent from my phone.
On Oct 31, 2012 10:04 AM, "Joe Warren-Meeks"
wrote:
> On 31 October 2012 00:42, Curtis C. wrote:
> > On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
> > w
have you tried to disable vnc and check if is working?
I followed official doc using multi_host. This is my vnc configs
#VNC CONSOLE
--vnc_enabled=true
--vncproxy_url=http://cloud-controller-ip:6080
--vnc_console_proxy_url=http://cloud-controller-ip:6080
--novnc_enabled=true
--novncproxy_base_ur
On 31 October 2012 00:42, Curtis C. wrote:
> On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
> wrote:
>> Hi guys,
>>
>> Can someone point me in the direction of a guide to get Openstack
>> working with two nodes, one as controller and the second as a compute
>> node, please?
>>
>> I've tried th
I wanted to throw in my two cents here. I generally agree with the
notion that we should have the ability to issue tokens with different
scopes. And that this will become increasingly useful down the road
as we seek to provide finer grained access control for each user.
Having said this, I do hav
I'm okay with "Starting Tokens".
-jOrGe W.
On Oct 23, 2012, at 7:25 AM, Adam Young wrote:
On 10/23/2012 01:25 AM, Jorge Williams wrote:
Here's my view:
On making the default token a configuration option: Like the idea. Disabling
the option by default. That's fine too.
On scoping a token to
Your suggestion to it optional (it being a token scoped to multiple projects).
:)
From: Adam Young [mailto:ayo...@redhat.com]
Sent: Monday, October 22, 2012 9:57 PM
To: Jorge Williams
Cc: Joe Savak; OpenStack Development Mailing List; openstack@lists.launchpad.net
Subject: Re: [Openstack] Fwd
On 10/23/2012 01:25 AM, Jorge Williams wrote:
Here's my view:
On making the default token a configuration option: Like the idea.
Disabling the option by default. That's fine too.
On scoping a token to a specific endpoint: That's fine, though I
believe that that's in the API today. Curre
Here's my view:
On making the default token a configuration option: Like the idea. Disabling
the option by default. That's fine too.
On scoping a token to a specific endpoint: That's fine, though I believe that
that's in the API today. Currently, the way that we scope tokens to endpoints
Are you guys +1 ing the original Idea, my suggestion to make it
optional, the fact that I think we should call these sloppy tokens?
On 10/22/2012 03:40 PM, Jorge Williams wrote:
+1 here too.
At the end of the day, we'd like the identity API to be flexible
enough to allow the token to be scope
+1 here too.
At the end of the day, we'd like the identity API to be flexible enough to
allow the token to be scoped in a manner that the deployer sees fit. What the
keystone implementation does by default is a different matter -- and disabling
multiple tenant scope by default would be fine b
On Oct 21, 2012 12:11 PM, "Joe Savak" wrote:
>
> +1. ;)
>
> So the issue is that the v2 API contract allows a token to be scoped to
multiple tenants. For v3, I'd like to have the same flexibility. I don't
see security issues, as if a token were to be sniffed you can change the
password of the acco
+1. ;)
So the issue is that the v2 API contract allows a token to be scoped to
multiple tenants. For v3, I'd like to have the same flexibility. I don't see
security issues, as if a token were to be sniffed you can change the password
of the account using it and use those creds to scope tokens t
On 10/20/2012 01:50 PM, heckj wrote:
I sent this to the openstack-dev list, and thought I'd double post
this onto the openstack list at Launchpad for additional feedback.
-joe
Begin forwarded message:
*From: *heckj mailto:he...@mac.com>>
*Subject: **[openstack-dev] [keystone] Tokens represent
I sent this to the openstack-dev list, and thought I'd double post this onto
the openstack list at Launchpad for additional feedback.
-joe
Begin forwarded message:
> From: heckj
> Subject: [openstack-dev] [keystone] Tokens representing authorization to
> projects/tenants in the Keystone V3 API
-- Forwarded message --
From: Duncan McGreggor
Date: Mon, Sep 3, 2012 at 12:40 AM
Subject: Re: [openstack-dev] Running for Quantum PTL
To: OpenStack Development Mailing List
On Sun, Sep 2, 2012 at 2:10 PM, Dan Wendlandt wrote:
> Hi folks,
>
> I'm really excited about what we've
26 matches
Mail list logo