Hi Anne :-)I think it only doesn't applies to- ESX- QEMU- LXCWhile it has been implemented on the other hypervisors technologies :http://wiki.openstack.org/HypervisorSupportMatrixMaybe some doc update needed around ?Later,Razique
Nuage Co - Razique Mahrouarazique.mahr...@gmail.com
Le 24 avr.
Hi
Martin
Now I have let the vnc working.
install 3 package
nova-consoleauth python-novnc novnc
modify the nova.conf
#novnc
--novnc_enabled=true
--novncproxy_base_url= http://10.42.0.6:6080/vnc_auto.html
--vncserver_proxyclient_address=127.0.0.1
--vncserver_listen=127.0.0.1
restart service
Hello everyone.
My setup is simple. A volumen shared by iSCSI from our Netapp storage
that I would like to use it for the instances running on our
nova-compute nodes.
Has anyone tried to use OCFS2 or GFS2 as FS via iSCSI mounted on the
nova-computes as a sharing disk and running the instances
Robbie Williamson wrote:
For those of you who may have missed this announcement. Canonical has
created the Ubuntu Cloud archive. Starting with the Folsum release,
Folsom :)
users will be able to elect to enable this archive, and install newer
releases of OpenStack (and the dependencies) as
Hello everyone,
Our weekly project release status meeting will take place at 21:00 UTC
this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it,
please name a substitute on [2].
We'll discuss the outcome of the design summit, and how to properly
specify Folsom plans going forward.
Hi Everyone,
i've been looking through wsgi code, and i have found a lot of
duplicated code between all the projects. Running a quick and dirty search,
i get the following numbers (just focusing on glance horizon keystone
nova openstack-common quantum swift projects):
- There are 87
On 04/23/2012 10:45 PM, Doug Hellmann wrote:
On Mon, Apr 23, 2012 at 4:14 PM, Brian Schott
brian.sch...@nimbisservices.com
mailto:brian.sch...@nimbisservices.com wrote:
Doug,
Do we mirror the table structure of nova, etc. and add
created/modified columns?
Or do
I think we have support for this currently in some fashion, Dragon?
-S
On 04/24/2012 12:55 AM, Loic Dachary wrote:
Metering needs to account for the volume of data sent to external network
destinations ( i.e. n4 in http://wiki.openstack.org/EfficientMetering ) or
the disk I/O etc. This
23. apr. 2012 17.15 skrev Justin Santa Barbara jus...@fathomdb.com:
What's the advantage of replacing the native EC2 compatibility layer with
AWSOME from a user / operator point of view?
Although I wasn't able to attend the design summit session, right now we
have two native APIs, which means
Due to the redirect nature of the auth system we may need JSONP support
for this to work.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
Hi all,
The feature comparison matrix at
http://wiki.openstack.org/Nova/APIFeatureComparison has a row labelled
AMI's backed by EBS, which suggests to me that there is a way to have
nova-compute start a VM with its root store managed by nova-volume. But
I haven't been able to find anything that
Dan,
I've updated the question (few more queries)
Also, you didn't say exactly how you were running devstack. Can you send
your config?
I've described my two-machine setup in the original question itself.
I didn't know how to add an attachment to the question, so here is my nova.conf
for
Hi Ghe,
On Tue, 2012-04-24 at 12:15 +0200, Ghe Rivero wrote:
Hi Everyone,
i've been looking through wsgi code, and i have found a lot of
duplicated code between all the projects.
Thanks for looking into this. It sounds quite daunting.
I wonder could we do this iteratively by extract the
On Tue, 2012-04-24 at 13:26 +0200, Soren Hansen wrote:
23. apr. 2012 17.15 skrev Justin Santa Barbara jus...@fathomdb.com:
With one native API, we can focus all our energies on making sure that API
works. Then, knowing that the native API works, we can build other APIs on
top through
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the somewhat generic name of 'compute.instance.exists' and is
emitted on an periodic basis, currently by a cronjob.
Currently, we only populate bandwidth data from XenServer, but if the hook is
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the somewhat generic name of 'compute.instance.exists' and is
emitted on an periodic basis, currently by a cronjob.
Currently, we only populate bandwidth
JSONP is great, but won't work with POST requests.
I don't quite understand what Due to the redirect nature of the auth
system means, though.
If I use a custom Webkit browser allow cross domain XMLHttpRequests it
works fine - I do a POST to /v2.0/tokens, get the token and then use that.
What am
On 04/24/2012 10:19 AM, Nick Lothian wrote:
JSONP is great, but won't work with POST requests.
I don't quite understand what Due to the redirect nature of the auth
system means, though.
Sorry, I am working on a few things that are related. OpenID and
various other systems have issues along
Hi John
+1 would be interested for monthly meeting. Time is ok.
Alan
From: openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net
[mailto:openstack-bounces+alan.kavanagh=ericsson@lists.launchpad.net] On
Behalf Of John Garbutt
Sent: April-23-12
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the somewhat generic name of 'compute.instance.exists' and is
emitted on an periodic basis, currently by a
If EC2 API is limiting what we can do, that's not going to change just
because you move the EC2 API implementation into a proxy in front of the
OpenStack API. The only difference is that it's suddenly the AWSOME
development team's problem.
I think it's actually the EC2 API caller's problem.
On 04/24/2012 11:19 AM, Nick Lothian wrote:
JSONP is great, but won't work with POST requests.
Hmm, good point.
I don't quite understand what Due to the redirect nature of the auth
system means, though.
If I use a custom Webkit browser allow cross domain XMLHttpRequests it
works fine
On Apr 24, 2012, at 9:28 AM, Ghe Rivero wrote:
On Tue, Apr 24, 2012 at 2:40 PM, Mark McLoughlin mar...@redhat.com wrote:
Hi Ghe,
On Tue, 2012-04-24 at 12:15 +0200, Ghe Rivero wrote:
Hi Everyone,
i've been looking through wsgi code, and i have found a lot of
duplicated code
As far as I know, the current volume service doesn't support
connecting the same volume to multiple instances at the same time, so
neither of these can work directly through nova apis.
-nld
On Tue, Apr 24, 2012 at 4:44 AM, Daniel Martinez danie...@gmail.com wrote:
Hello everyone.
My setup is
I'd be interest to join too. Shall we use a wiki page to collate names
and affiliations of people interested (there's a Launchpad group set
up by the way - https://launchpad.net/~openstack-xenapi), as well as
meeting details?
Thanks,
Armando
On Tue, Apr 24, 2012 at 3:32 PM, Alan Kavanagh
Actually, I think JSON schema for our message-bus messages might be a really
good idea (tm). Violations could just be warnings until we get things locked
down... maybe I should propose a blueprint? (Although I have enough of a
blueprint backlog as it is...)
Actually, I think JSON schema for our message-bus messages might be a really
good idea (tm). Violations could just be warnings until we get things locked
down... maybe I should propose a blueprint? (Although I have enough of a
blueprint backlog as it is...)
This was discussed at the
Hi,
Heat is a AWS CloudForm API implementation for OpenStack. The purpose
of the software is to orchestrate resources (including virtual machines,
networks, storage) into a running cloud application. The software
converts an AWS template into native OpenStack API calls and provides a
REST API
Good plan, I have started a wiki page to capture that stuff:
http://wiki.openstack.org/XenAPIMeetings
Cheers,
John
-Original Message-
From: Armando Migliaccio [mailto:amigliac...@internap.com]
Sent: 24 April 2012 16:23
To: Alan Kavanagh
Cc: John Garbutt;
Hi Ghe,
I suppose it will be very useful. We are planning to create a new project
for nova-volumes (cider?) and I’m sure it will have same duplicate classes.
Sooner we will have a common openstack layer is better.
Regards,
-Vladimir
*From:*
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each
instance The event has the somewhat generic name of
'compute.instance.exists'
Nick,
I know you said 'serverless clients' but you have to be serving the js from
somewhere right?
If you are using nginx it can be as simple as:
location /nova/ {
proxy_pass: http://nova-api.trystack.org;
}
then you can POST to yourserver/nova/v.02/. from the browser
etc.
(it's just
On Apr 24, 2012, at 10:55 AM, Thompson Lee wrote:
On Apr 24, 2012, at 9:28 AM, Ghe Rivero wrote:
I have plans to try to move as much as possible into openstack-common. I
will start with nova as a test bed and see what we get from there. My future
plans include db code and tests (in the
On 04/24/2012 11:39 AM, Eric Windisch wrote:
Actually, I think JSON schema for our message-bus messages might be a
really good idea (tm). Violations could just be warnings until we get
things locked down... maybe I should propose a blueprint? (Although I
have enough of a blueprint backlog as
Thanks for the pointer. I found the etherpad:
http://etherpad.openstack.org/VersioningNovaRPCAPIs
Is there a blueprint that came / is coming out of that?
I think the data representation is orthogonal e.g. in theory, we could even
use XML schemas:
PyDict -- XML -- XML Schema Validation -- Warn /
+1 and good on the time here
On Apr 23, 2012, at 10:21 AM, John Garbutt john.garb...@citrix.com wrote:
Hi,
Are people keen for a XenAPI virt layer meetup on IRC every month?
I have added a suggested time to the wiki, as a starting point:
Monthly, second Wednesday at 17:00 UTC
Does
Jsonp sucks (get only) but might be the best choice. That's generally how AWS
supports these use cases, fwiw.
On Apr 24, 2012, at 7:49 AM, Sandy Walsh sandy.wa...@rackspace.com wrote:
On 04/24/2012 11:19 AM, Nick Lothian wrote:
JSONP is great, but won't work with POST requests.
Hmm,
I'm more in favor of just having a schema, I don't care if that compiles to
protocol buffers, json, NEWAWESOMEhipsterMSGFORMAT.
That schema will force people to think a little more when they add messages,
and it will automatically document the messages that are being sent around.
That's a big
The JS may be served from a CDN. You can't assume a server-side proxy. Here's
an example of a sever-less JS application that communicates directly to EC2:
http://aws.amazon.com/developertools/1424 (there are versions for other
services like SQS and SDB as well). Server-less JS applications are
The change was just to the fake rpc backend to help catch more errors in
unit tests where non-primitive types are getting passed into rpc.
My current code should still work, but the tests seem to have eliminated the
more generic exception handling case with the assumption that testing
Probably an extra audit system is required. I'm searching for solutions in
the IT market.
Regards
On Tue, Apr 24, 2012 at 6:00 PM, Loic Dachary l...@enovance.com wrote:
**
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06
Good, +1 from me.
Thanks,
Hitesh Wadekar
On Tue, Apr 24, 2012 at 9:14 PM, John Garbutt john.garb...@citrix.comwrote:
Good plan, I have started a wiki page to capture that stuff:
http://wiki.openstack.org/XenAPIMeetings
Cheers,
John
-Original Message-
From: Armando Migliaccio
Hi Monsyne,
I have set the notification_driver param, but no notification.* queues
created. I'm using devstack stable/essex.
stack@ubuntu:/$ sudo rabbitmqctl list_queues
Listing queues ...
volume_fanout_e0923a8bbb9f45dc9e63d382796a4c8f 0
cert.ubuntu 0
consoleauth.ubuntu 0
compute 0
On 04/24/2012 01:25 PM, Joshua Harlow wrote:
I’m more in favor of just having a schema, I don’t care if that compiles
to protocol buffers, json, NEWAWESOMEhipsterMSGFORMAT.
That schema will force people to think a little more when they add
messages, and it will automatically document the
Hello
It's very cool.
I send review request to review.openstack.org this a link to it
https://review.openstack.org/#/c/6775/
Thank you,
Victor
2012/4/23 Doug Hellmann doug.hellm...@dreamhost.com:
This sounds like a good candidate to live in openstack-common, rather than
being limited to
I take it that the instance manager doesn't generate any kind of heartbeat, so
whatever monitoring/archiving service we do should internally poll the status
over MQ?
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph:
What do you mean by connecting at the same time? The semantics of a block
service is that a volume is mounted by a single user at a time.
When you want something more complex you should build that with a proxy on top
of the base service. What you are talking about is a very
Specialized need with
Hi, guys,
Can I ask some questions beyond OpenStack? If yes, who can give me some
hints that if I need to design a datacenter, I have request numbers I need
to process per day, different types of servers. How can I compute the
processing time for each request, and how to decide the number of
This kind of messages are coming from nova exchange aprox. each 60 secs
Can be this considered as a heartbeat for you?
[x] Received '{_context_roles: [admin], _msg_id:
a2d13735baad4613b89c6132e0fa8302, _context_read_deleted: no,
_context_request_id: req-d7ffbe78-7a9c-4d20-9ac5-3e56951526fe,
Yeah, but does that mean the instance is alive and billable :-)? I guess that
counts! I thought they were only in response to external API/admin requests.
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph: 443-274-6064
Having endpoints under the service construct is supposed to make it easier to
programmatically find the endpoint(s) you are interested in.
For example - as nova client I can parse the service catalog and identity nova
by service-type compute in order to get the public, internal, and admin
Hi All,
I would like to propose a minimum required code coverage level per file in
Nova. Say 80%. This would mean that any new feature/file should only be
accepted if it has over 80% code coverage. Exceptions to this rule would
be allowed for code that is covered by skipped tests (as long as
I think so.
If it is in response or not, it's a truly heartbeat
On Tue, Apr 24, 2012 at 9:46 PM, Brian Schott
brian.sch...@nimbisservices.com wrote:
Yeah, but does that mean the instance is alive and billable :-)? I guess
that counts! I thought they were only in response to external
On Apr 24, 2012, at 11:00 AM, Loic Dachary wrote:
On 04/24/2012 04:45 PM, Monsyne Dragon wrote:
On Apr 24, 2012, at 9:03 AM, Loic Dachary wrote:
On 04/24/2012 03:06 PM, Monsyne Dragon wrote:
Yes, we emit bandwidth (bytes in/out) on a per VIF basis from each instance
The event has the
On Apr 24, 2012, at 2:31 PM, Brian Schott wrote:
I take it that the instance manager doesn't generate any kind of heartbeat, so
whatever monitoring/archiving service we do should internally poll the status
over MQ?
Actually, it generates periodic 'heartbeat' events ('exists' events) for each
On Apr 24, 2012, at 2:46 PM, Brian Schott wrote:
Yeah, but does that mean the instance is alive and billable :-)? I guess that
counts! I thought they were only in response to external API/admin requests.
-
Brian Schott, CTO
Nimbis Services,
On Tue, Apr 24, 2012 at 1:11 PM, Joe Gordon j...@cloudscaling.com wrote:
Hi All,
I would like to propose a minimum required code coverage level per file in
Nova. Say 80%. This would mean that any new feature/file should only be
accepted if it has over 80% code coverage. Exceptions to this
On Apr 17, 2012, at 2:04 AM, William Herry wrote:
so, what changes should I make if I want use raw in openstack, I didn't find
some configure option in nova.conf.sample
I also try to modify the source code in nova/virt/libvirt/utils.py, and
didn't succeed
I noticed that the type of
+1
From: openstack-bounces+nayna.patel=hp@lists.launchpad.net
[mailto:openstack-bounces+nayna.patel=hp@lists.launchpad.net] On Behalf Of
Dan Wendlandt
Sent: Tuesday, April 24, 2012 2:58 PM
To: Joe Gordon
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [OpenStack][Nova]
What changes would be needed to make qcow2 files work as snapshots?
Some type of image dependency management in glance (and failure cases) and
the corresponding dependency fetching in nova (and failure cases)?
Might be something pretty useful to have, instead of forcing raw for snapshots?
On
John,
Please count me in as well.
Wu
Sent from my iPad
On Apr 24, 2012, at 11:44 PM, John Garbutt john.garb...@citrix.com wrote:
Good plan, I have started a wiki page to capture that stuff:
http://wiki.openstack.org/XenAPIMeetings
Cheers,
John
-Original Message-
From:
Joshua Harlow wrote:
What changes would be needed to make qcow2 files work as snapshots?
Some type of image dependency management in glance (and failure cases) and
the corresponding dependency fetching in nova (and failure cases)?
Might be something pretty useful to have, instead of forcing
Ok, but forcing a new block storage project to have this feature, is that the
right way?
Maybe it will, just wondering.
Glance seems to be the registry of images, so a natural progression is that it
can maintain the image dependencies?
This would allow the qcow2 image to pull the needed
Javascript *can* set custom headers, but only by using XMLHttpRequest. That
cannot work cross-domain unless the appropriate CORS headers are set.
Hence this issue :)
On Apr 25, 2012 12:21 AM, Adam Young ayo...@redhat.com wrote:
On 04/24/2012 10:19 AM, Nick Lothian wrote:
JSONP is great, but
I actually like JSONP, but supporting it would be quite a substantial
change to the APIs
Adding CORS support is a relatively small change, and probably a more
technically correct solution.
It does have less browser support though.
On Apr 25, 2012 4:01 AM, Tres Henry t...@treshenry.net wrote:
Yes, this will work if I know in advance what server I will be connecting
too.
However, it does remove the ability to support any cloud without
intervention on the serverside.
On Apr 25, 2012 2:46 AM, Joel Semar sema...@gmail.com wrote:
Nick,
I know you said 'serverless clients' but you have
The solution until the webservice deliver that headers is:
Solution 1:
1. Put the webservice behind a remote or local proxy
2. Apply some a filter (decorator) for each response with the CORS headers
(in the proxy) in order to trick the browser
Solution 2:
Some time ago I tested it with Chrome
So, why such a focus on this? IMO both JSONP and CORS are way too early stage
to adopt and the security risks outweigh the rewards. Usually, I see people
doing this to enable mashups across separate providers.
Just curious why the focus/need is perceived in the community? If this is
really
On Apr 24, 2012, at 4:11 PM, Joe Gordon wrote:
Hi All,
I would like to propose a minimum required code coverage level per file in
Nova. Say 80%. This would mean that any new feature/file should only be
accepted if it has over 80% code coverage. Exceptions to this rule would be
./etc/default_catalog.template is not a good default for template_file,
I agree. But /etc/keystone/catalog.template or similar would be a fine
default to include in the code. The tests would override the default
As for error messages - I completely agree we should have good error
handling like
70 matches
Mail list logo
