Thanks for the replies.
My actual question was regarding euca-attach-volume. I could run
euca-attach-volume from host successfully. But from guest I could not find a
new disk.
Regards,
Haynes
-Original Message-
From: openstack-bounces+haynes.davis=accenture@lists.launchpad.net
I've noticed euca-attach-volume wont complain if you give it bad args...
Try using /dev/vdc as the device, and check dmesg | tail inside the instance
after...
Kiall
Sent from a mobile - sorry for being short!
On Oct 10, 2011 6:57 a.m., haynes.da...@accenture.com wrote:
Thanks for the replies.
Hi Paul,
thanks a lot for your answer.
I'll have a deeper look at XS6 to make sure it does what I need.
Cheers,
Giuseppe
2011/10/7 Paul Voccio paul.voc...@rackspace.com:
Hi Guiseppe,
Sorry for the delay in the response. Looking at the differences in the
allowed operations, I have the
Hello Everyone,
I am considering installinig OpenStack on 20 of our servers, and I was wondering
if it was possible to:
1) Share CPUs, RAM (RDMA) and ports across the Host servers (not VMs)
2) Load balancing across multiple hosts
I know that shared storage is possible, I am wondering about the
when I click lunch images in dashboard. The console will show error:
Traceback (most recent call last):
File /usr/lib/pymodules/python2.7/eventlet/greenpool.py, line 80, in
_spawn_n_impl
func(*args, **kwargs)
File /usr/lib/pymodules/python2.7/eventlet/wsgi.py, line 508, in
process_request
Hiya,
After deleting a security group, new instances fail to create due to the
error below, I've restored the group via the DB (its the puppet group with
id 6) and all is well again.
Is this expected/a known issue/etc or am I doing something wrong? If I'm
not, can you let me know so I can file a
I should have added, this is the 2011.3-0ubuntu6 version running on Ubuntu
Oneiric, installed from the Ubuntu archives.
Thanks,
Kiall
On Mon, Oct 10, 2011 at 10:32 AM, Kiall Mac Innes ki...@managedit.iewrote:
Hiya,
After deleting a security group, new instances fail to create due to the
My .02 -
Pretty much every Open Source project I've been involved in has two lists set
up like this, once they get off the ground. Like others have said, it doesn't
mean the groups separate, only that the discussions are easier to follow...
Cheers,
--
Mark Nottingham http://www.mnot.net/
Hi Mark,
That part I understand :) Consider these rules (nabbed from forum posting
herehttp://www.zeroshell.net/eng/forum/viewtopic.php?p=655sid=76f8a08777176b9f939642734f2b23d0#655
):
iptables -t nat -A prerouting_rule -d WAN_IP -p tcp --dport 80 -j DNAT --to
192.168.0.10
iptables -A
Hi Kiall,
On Sun, 2011-10-09 at 22:41 +0100, Kiall Mac Innes wrote:
Hiya,
I'm looking to find out if there is any way to access an instance via its
public (floating ip) from within the same instance.
The docs mention that this is not possible here:
Hi,
I've got an issue with CLI Glance and Keystone authentication.
I try the above method with env variables, but I get this error:
# glance -d index
Traceback (most recent call last):
File /usr/bin/glance, line 1206, in module
result = command(options, args)
File /usr/bin/glance, line 60,
On Mon, 2011-10-10 at 12:58 +0100, Mark McLoughlin wrote:
On Mon, 2011-10-10 at 12:29 +0100, Kiall Mac Innes wrote:
Hi Mark,
That part I understand :) Consider these rules (nabbed from forum posting
Hello,
I'm trying to get the openstack mailing list subscribed to Gmane[0], and
I'm not sure if we need some from the Openstack mailing list
administrators, or what the situation is. I've decided to CC the
openstack list to keep people informed of the situation.
On Thu, 06 Oct 2011 21:22:06
In talking with several people at the Design Summit about the OpenStack Compute
API, I have come to the conclusion that our current method of versioning is
broken. I would like to propose that as we move forward, we adopt the following
API versioning conventions:
1) Use a three-part version
On Thu, Oct 6, 2011 at 3:49 PM, Kuo Hugo tonyt...@gmail.com wrote:
3. We can using cloud with Dashbord smoothly for basic usage. So does
nova-client . I found that nova-client CLI tool could not
add-key-pair/show-keypair ...I think it's fine , just add it direct from API
endpoint . But the
Hi Haynes -
We just updated the documentation after learning that when you're running
KVM, the actual device name in the guest will be different than the one
specified in the attach command. (doc bug
linkhttps://bugs.launchpad.net/openstack-manuals/+bug/868595)
Thanks Razique Mahroua for making
Just to clear up some questions I have already gotten: The revision numbers are
designed only to advertise additions to the spec, wether they be new fields or
whole resources. The revision number does not advance if we make a bug fix
within Nova, as the spec itself needs to evolve independently
Thank you to all who attended the OpenStack design summit last week
and expressed their interest and support for the ongoing efforts
around quality assurance in OpenStack.
As a reminder, if you are interested in participating in the OpenStack
QA community, please do join the Launchpad team here:
Thanks for Grid Dynamic ,
I do use it already : . Really useful to fire up instance via nova with
GridDynamic branch.
If the branch could assign keypair will be great , and an additional
recommend is that nova client should run with a default keypair if users do
not specify any keypair for booting
Dont know if share is what im going to answer but a cluster of computes
nodes shares they resources, if you use an scheduler that fits your needs to
balance trought the computes resources will be ok.
Load balancing of instances comes with the scheduler you choose too. But if
youre referring to
Thierry pointed out that in my summary email of QA decisions, I forgot
to mention what day the weekly QA meeting is on.
The weekly QA meeting is on Wednesday, at 12:00 EDT (16:00 UTC).
Thanks all!
-jay
___
Mailing list:
Looks cool! When do you think you'll be ready to propose these changes back
into trunk?
A
On Mon, Oct 10, 2011 at 7:32 AM, Dmitry Maslennikov
dmaslenni...@griddynamics.com wrote:
On Thu, Oct 6, 2011 at 3:49 PM, Kuo Hugo tonyt...@gmail.com wrote:
3. We can using cloud with Dashbord smoothly
I'd like to try to summarize and propose at least one next step for the content
of the openstack-integration-tests git repository. Note that this is only
about the actual tests themselves, and says absolutely nothing about any gating
decisions made in other sessions.
First, there was
Donabe: http://etherpad.openstack.org/Donabe
thx
debo
-Original Message-
From: openstack-bounces+dedutta=cisco@lists.launchpad.net
[mailto:openstack-bounces+dedutta=cisco@lists.launchpad.net] On
Behalf Of bob.bl...@calxeda.com
Sent: Monday, October 10, 2011 9:23 AM
To:
I'm still waiting for folks to fill in some of the details, but here's a
wiki page with pointers to Quantum/NetStack related sessions and
presentations at the Essex summit:
http://wiki.openstack.org/NetstackEssexSummit
Dan
On Mon, Oct 10, 2011 at 1:26 PM, Debo Dutta (dedutta)
On Fri, 2011-10-07 at 10:11 -0500, Anne Gentle wrote:
Link is:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Since you mention this list, I was asked in Boston by the
'spring-cleaning-department': why do we have some lists that seem
abandoned on
Yep, I think we're in agreement. Version 1 should always be backwards
compatible. Once we need to make a backwards incompatible change, we need to
talk about version 2.
Waldon
On Oct 10, 2011, at 2:11 PM, George Reese wrote:
API implementations should always be backwards compatible. The
One of those folks just filled the details he could fill!
Salvatore
From: openstack-bounces+salvatore.orlando=eu.citrix@lists.launchpad.net
[mailto:openstack-bounces+salvatore.orlando=eu.citrix@lists.launchpad.net]
On Behalf Of Dan Wendlandt
Sent: 10 October 2011 18:52
To: Debo Dutta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2011 05:01 PM, Jason Kölker wrote:
nameserver 10.0.1.1
How does nova assign the nameserver to the VMs? Can I change it someone
so it has 8.8.4.4?
I assume you are using Vlan or Flatdhcp? If so add --dns-server=8.8.4.4
to your flags
On Mon, 2011-10-10 at 16:07 -0400, Sharif Islam wrote:
I am still stuck with this problem: my instances can ping only with ip
addresses. I deleted nova-network and created it again and then fired up
an instance. But still resolv.conf shows nameserver 10.0.1.1. I only
have one instance running
This is a bug that is a result of changing the behavior of source groups. For
a while we emulated the old style aws source group style that doesn't allow
specifying protocol and ports. This was changed recently and it looks like
this check was missed.
Vish
On Oct 6, 2011, at 6:20 AM,
The injection only works with ubuntu images, so ttylinux is out. I'm not sure
why it wasn't working for you. Metadata will not work in flat mode unless you
specifically create forwarding rules, so using ubuntu cloud images you might
have to wait for the request to time out. Not sure why it
I used devstack script to install openstack and use openstack in our
company. Now there are bug be found and be fixed, I need upgrade the
openstack in my machine? How can I do that upgrade?
--
非淡薄无以明志，非宁静无以致远
___
Mailing list:
Actually right now it doesn't re-check out.
You have to manually pull in the project you want to update.
I've got a patch that I want to get reviewed / fixed before I merge
https://github.com/cloudbuilders/devstack/pull/52 that will update the
repos on each run.
Jesse
2011/10/10 Joseph Heck
Where would these versions show up? In URLs? In documentation? In response
payloads?
If they show up in URLs, then every backwards-compatible change would be made
into a backwards-incompatible change. E.g., if you had
http://www.example.com/v1.2.3/foo
as a resource, and adding a new resource
On 19/09/2011, at 4:03 PM, Mark McLoughlin wrote:
OTOH, POST to update the object's metadata doesn't make much sense. We
don't accept the entity enclosed in the request as a new subordinate.
PATCH[1] would probably have made more sense.
The spec is actually quite clear on the different
36 matches
Mail list logo
