My understanding is that you would not always want a user to delete an
instance in an error state. So an operations person can figure out what
went wrong. I think the instances that are in error state do not count
against the quota but i agree that they clutter up the API calls to list
servers.
I
From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of
Marton Kiss [marton.k...@gmail.com]
Sent: Thursday, March 22, 2012 11:14 AM
To: Debo Dutta (dedutta)
Cc: openstack@l
Instances in deleted status can normally be deleted, but there is definitely a
bug to file here somewhere – possibly more than one. A common reason I have
seen is that the node the instance lives on is no longer operating correctly,
so the compute manager never gets the delete request, so it do
Ustream broadcast as an alternative option?
Marton Kiss, CTO
Xemeti
On Mar 21, 2012 11:54 PM, "Debo Dutta (dedutta)" wrote:
> SW side: Another option would be to run webex meetings or even google
> hangout!
>
> debo
>
> -Original Message-
> From: openstack-bounces+dedutta=cisco@lists
why not allow "nova delete" and "euca-terminate " to delete the instance with "error" status?Yong Sheng Gong-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Guilherme Birk , Openstack Mail List From: Mandar Vaze Sent by: openstack-bounces+gongysh=cn.ibm@lists.launch
I agree user shouldn’t have to update DB.
There needs to be some periodic cleanup task that “fixes” the
vm_state/task_state for “stuck” instances.
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net]
Apologies for my previous email.
I did not realize you were referring to a domU kernel. My crash was on a dom0
kernel.
Salvatore
From: openstack-bounces+salvatore.orlando=eu.citrix@lists.launchpad.net
[mailto:openstack-bounces+salvatore.orlando=eu.citrix@lists.launchpad.net]
On Behalf
It's not a trailing slash on the URL sent to keystone. It's a trailing slash in
the Horizon setting which leads to a double-slash in the URL sent to keystone.
- Gabriel
From: anti...@gmail.com [mailto:anti...@gmail.com] On Behalf Of Dolph Mathews
Sent: Wednesday, March 21, 2012 5:26 PM
Wasn't this fixed in keystoneclient (properly handling an unexpected
trailing slash)?
-Dolph
On Wed, Mar 21, 2012 at 6:56 PM, Gabriel Hurley
wrote:
> It looks like you’ve got an extra slash in your URL. That probably means
> you’ve got a trailing slash on your OPENSTACK_KEYSTONE_URL setting. As
It looks like you've got an extra slash in your URL. That probably means you've
got a trailing slash on your OPENSTACK_KEYSTONE_URL setting. As per the example
settings file it should look like this:
OPENSTACK_KEYSTONE_URL = "http://%s:5000/v2.0"; % OPENSTACK_HOST
e.g.
OPENSTACK_KEYSTONE_URL =
Hi everyone,
I want to understand the different possibilities to deploy Openstack Nova in a
site with thousands of hosts. After reading the documentation and following the
list for some time now I’m confused how to use the concepts: “region”,
“availability zone”, “cell”, “host aggregate”… to hav
Hello,
I have installed horizon dash board from git and integrating with nova. When I
login to dashboard, I am getting error. Error: please try logging again.
In dashboard log, I see the following error:
Request returned failure status.
In keystone log, I see
2012-03-21 15:37:02 DEBUG [route
SW side: Another option would be to run webex meetings or even google
hangout!
debo
-Original Message-
From: openstack-bounces+dedutta=cisco@lists.launchpad.net
[mailto:openstack-bounces+dedutta=cisco@lists.launchpad.net] On
Behalf Of Stefano Maffulli
Sent: Wednesday, March 21,
I'm still loooking for *hardware* to make this happen.
Lets try to make this more sexy and see where to cook hackers are: what
if we buy a few beaglebone boards ($89 each) and spend a weekend hacking
a streaming server on them?
The boards are cheap enough and should have enough power to acquire
I recently had a (probably) similar issue, with xcp-squeezed consuming all the
memory and then causing a reboot.
I was using a pae kernel (3.0.0-16.generic.pae), and the workaround, as
suggested by the Kronos team, was to increase dom0 memory with a boot parameter
to the hypervisor. I used dom0_
I've never seen that kernel panic before. If you're building on an NFS share
though, that often screws up the permissions. You could have root-squashing
turned on, and then every file that's supposed to be owned by root is owned by
an unprivileged user instead. It wouldn't surprise me that th
I have tried to throw together some pictures that help describe the guest
networking modes with XenServer:
http://wiki.openstack.org/XenServer/NetworkingFlags
The idea is to complement the existing diagrams currently in the manuals.
It would be great if someone can review these diagrams for me.
Hi everyone,
apologies for the cross-post; I believe this might be interesting to
people on both the openstack and the pacemaker lists. Please see
below.
On Tue, Feb 14, 2012 at 9:07 AM, i3D.net - Tristan van Bokkem
wrote:
> Hi Stackers,
>
> It seems running Openstack components in High Availabi
Narayan, I completely agree with you. Developers are our "first line of
defense", but they are not the only one. I would love to have different
environments (development, SMB deployments, large scale deployments), where
all of them have the same behavior, but i'm afraid there is already a long
road
On 03/21/2012 08:48 PM, Narayan Desai wrote:
> Ghe, while you're right that these two workloads are different,
> deployers need developers to use a representative environment during
> development, or the code doesn't work when it hits real deployments.
> We've now been bitten during our initial dep
horizon/openstack_dashboard/settings.py
--
Mike Perez
DreamHost.com
On Wednesday, March 21, 2012 at 7:07 AM, Lucian Thomaz wrote:
> I'm trying use nova-billing with Horizon following the github page
> https://github.com/griddynamics/horizon-billing , but I can't find
> INSTALLED_APPS and HO
Hello,
I installed keystone (2011-3 version) and integrated with nova and glance
openstack. (diablo).
I am able to upload images and able to launch VMs. I am also able to ping and
ssh to private ip address of the launched VM.
However, I am trying to allocate a public/floating ip address.
euca-all
Dmitris:
Your best bet would be to take a look at the Quantum project:
https://launchpad.net/quantum
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
On Mar 15, 2012, at 10:25 AM, Dimitris Theodorou wrote:
> Hi,
>
> I am wo
Suyi:
There is some initial implementation work in this area:
https://review.openstack.org/5319
And there's a proposed session on SPICE in the upcoming design summit:
http://summit.openstack.org/sessions/view/4
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Servic
Just realized my reply was accidentally not sent to the list.
On Tue, Mar 20, 2012 at 2:03 PM, Todd Deshane wrote:
> Please post specific error messages.
>
> Some general suggestions inline.
>
> On Tue, Mar 20, 2012 at 12:56 PM, Alexandre Leites wrote:
>> Hi folks,
>>
>> First let me say that i'
I've actually not invalidated
https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/960070as
I originally and intentionally raised this in the ubuntu package.
This still makes me think its still a bug with the package as provided by
Ubuntu.
1) either install memcached as a dependency
Ah, George - thanks!
I'll erm.. invalidate that bug I raised too on that and put it down to not
reading the # comment regarding this issue in that file (I'm starting to
suck at this ;-))
Kev
On 21 March 2012 14:08, George Mihaiescu wrote:
> Hi Kevin,
>
> ** **
>
> Change these lines in “/e
Hi Kevin,
Change these lines in "/etc/openstack-dashboard/local_settings.py" and it
should fix the issue of being kicked off from Dashboard after logging in:
#CACHE_BACKEND = 'locmem://'
CACHE_BACKEND = 'dummy://'
SESSION_ENGINE = 'django.contrib.sessions.backends.cached_db'
Georg
I'm trying use nova-billing with Horizon following the github page
https://github.com/griddynamics/horizon-billing , but I can't find
INSTALLED_APPS and HORIZON_CONFIG in local_settings.py . Anyone can help with
that?
Lucian Thomaz
__
I'd like to see this cache somewhere that's not part of the document root
of my webserver - it forces me to one of 4 things
1) pre-create this directory and set appropriate permissions [but nothing
has told me to do this]
2) change permissions of my webserver to be non-secure (security risk is
min
It needs to create the directory in the first place to enable caching.. But
- If for whatever reason caching fails that should be no reason to blow up
and present an error.
Its probably worth highlighting this code is in python-novaclient, not
horizon. The vast majority of uses cases will be able
Ghe, while you're right that these two workloads are different, deployers
need developers to use a representative environment during development, or
the code doesn't work when it hits real deployments. We've now been bitten
during our initial deployment of cactus, our upgrade to diablo, and our
rec
On Tue, 2012-03-13 at 16:48 +, Pádraig Brady wrote:
> There are a few inconsistencies currently with
> the sqlalchemy version specifications in nova and glance.
>
> tl;dr SQLAlchemy>=0.6.3 should be fine for Essex?
Ok, I read your summary of this several times and got confused every
time.
Le
If the code should just ignore the fact it can't create this directory -
what is the point of it needing to attempt to create the directory in the
first place? What is its purpose if its superfluous?
try:
os.makedirs(cache_dir, 0755)
except OSError as e:
# NOTE(kiall): This is typicaly e
This is the only option? I've already done that, but it's kind "strange" I
update the database row everytime the script identifies a VM with error.
Date: Wed, 21 Mar 2012 09:39:03 +0800
Subject: Re: [Openstack] Can't delete instances with "error" status.
From: mwjpi...@gmail.com
To: guib...@hotm
This should fix the issue - https://review.openstack.org/5608
It duplicates the fix from 5-10 lines below now that the dot files have
been moved into a directory.
Thanks,
Kiall
On Wed, Mar 21, 2012 at 12:05 PM, Chuck Short wrote:
> On Wed, 21 Mar 2012 11:24:00 +
> Kevin Jackson wrote:
>
>
This sounds a lot like bug #897885 - In fact, the is nearly identical. I'll
submit a fix in a few mins..
https://bugs.launchpad.net/nova/+bug/897885
https://review.openstack.org/1952
Thanks,
Kiall
On Wed, Mar 21, 2012 at 11:24 AM, Kevin Jackson
wrote:
> Dear all,
> I could do with some help.
On Wed, 21 Mar 2012 11:24:00 +
Kevin Jackson wrote:
> Dear all,
> I could do with some help.
> I raised the following bugs in Horizon, specifically to do with
> Ubuntu.
>
> On a fresh install of Precise I do the following:
>
> apt-get update
> apt-get dist-upgrade
> reboot
> apt-get... nova
Dear all,
I could do with some help.
I raised the following bugs in Horizon, specifically to do with Ubuntu.
On a fresh install of Precise I do the following:
apt-get update
apt-get dist-upgrade
reboot
apt-get... nova, etc.
configure keystone etc
upload an image
all is good at this point
I then
Great work to all the teams :)# openstack ftw
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 21 mars 2012 à 11:14, Thierry Carrez a écrit :Thierry Carrez wrote:The tarball for the first release candidate for OpenStack Image Service(Glance) 2012.1 is now available at:https://launchpad.ne
Thierry Carrez wrote:
> The tarball for the first release candidate for OpenStack Image Service
> (Glance) 2012.1 is now available at:
>
> https://launchpad.net/horizon/essex/essex-rc1
Copy-paste error, should obviously read:
https://launchpad.net/glance/essex/essex-rc1
--
Thierry Carrez (ttx)
Hello everyone,
The tarball for the first release candidate for OpenStack Image Service
(Glance) 2012.1 is now available at:
https://launchpad.net/horizon/essex/essex-rc1
Unless release-critical issues are found that warrant a release
candidate respin, this RC1 will be formally released as the 2
"The lease file for dnsmasq is constantly updated by nova-network, thus
ensuring VMs get the IP address specified by the layer3 network driver (nova
IPAM or Melange)."
Sorry about that :)
> -Original Message-
> From: todd.deshane@gmail.com [mailto:todd.deshane@gmail.com]
> On Be
Hi,
we are facing two differents problems here. We have developers and
final users, and both of them with different expectations about what to get
from OpenStack. Developers wants an easy way to test "untested" code, new
cool-probably-broken features and be able to change immediately - devstack
44 matches
Mail list logo
