Hi all,
we have modified the Solaris volume driver code to work with Nexenta Block
Storage. Actually, we have succesfully deployed solutions with Nexenta and
Nova already.
You can check the code here:
https://github.com/StackOps/nova/tree/stable/diablo
So, we are happy to collaborate on this.
On Mon, 2011-11-14 at 10:22 +0100, Thierry Carrez wrote:
Mark McLoughlin wrote:
We still have a problem with versioning, though.
- Essex keystone will be 2012.1
- Diablo keystone was tagged as 2011.3
- Diablo keystone was actually versioned as 1.0 (see setup.py) even
Mark McLoughlin wrote:
You seem to be suggesting that incubating projects should follow a
different versioning scheme until they are accepted? I'd much rather see
incubating projects show that they can align themselves with the other
projects, rather than have them do something different.
Hi List,
I followed the Openstack training at Londen a few weeks ago, realy nice. I went
back to the office and standard building my Openstack test setup. There is just
one thing i can't get to work. Can someone help me on this one?
The Floating IPs works really nice when i use the API. The
Hi,
I have found something maybe bug in nova-network
ie: using FLATDHCP my br100 is set 10.200.200.2,hostname=node1
when I start nova-network, br100 will be add an other ip, maybe 10.200.200.5
here in nova db, fixed_ips table , 'host' field of address=10.200.200.5 entry
will be set to
All driver code is stamped with Apache Public License 2.0. Is it compatible
with OpenStack licensing model?
Currently driver supports Diablo branch of Nova, but we're working on
changes to make it work on master.
This driver was developed and tested in tight cooperation with Nexenta
team, and will
Hi all,
I'm trying to understand the multi-zone architecture of OpenStack.
I saw zone commands (list, show, select ...) have been added to the
OSAPI v1.1 (not as an extension but as a core component of the API)
but I cannot find any documentations in the OSAPI book:
Last time I had a conversation about this, I believe the goal was to refractor
and document Zone support as an extension to the core API. We're just not
there yet.
-jOrGe W.
On Nov 14, 2011, at 9:49 AM, Doude wrote:
Hi all,
I'm trying to understand the multi-zone architecture of
Hi Édouard -
I believe zones are documented in the Developer docs in
http://nova.openstack.org/devref/zone.html. The howto scenarios are
documented using the nova python client only currently (probably due to the
refactoring Jorge mentions).
When you run into these gaps, please do log a bug
Our team will be out in Seattle this week at the Supercomputing conference.
Anyone else planning to be there? Was looking for a BOF session but didn't see
one.
-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph:
Great! Nimbis Services is sharing a booth with Ohio Supercomputer Center booth
(#2713). If there are enough of us maybe we can crash a cloud-related BOF one
or pick a bar at one of the vendor parties :-).
Brian
PS: the company name, Nimbis Services, is supposed be a clever use of the
Thanks. I will drop by.
Prakashan Korambath
UCLA.
From: openstack-bounces+ppk=ats.ucla@lists.launchpad.net
[openstack-bounces+ppk=ats.ucla@lists.launchpad.net] On Behalf Of Brian
Schott [brian.sch...@nimbisservices.com]
Sent: Monday, November
Jorge is correct. The zones stuff was added before the API was finalized and
before the extensions mechanism was in place. We simply haven't taken the time
to convert it yet.
-S
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
Is the WADL for Nova and or its extensions available somewhere to look at?
Thanks,
Rupak Ganguly
Ph: 678-648-7434
On Fri, Oct 28, 2011 at 3:17 AM, Bryan Taylor btay...@rackspace.com wrote:
On 10/27/2011 05:52 PM, Mark Nottingham wrote:
Generating WADL (or anything else) from code is fine,
Hi Rupak -
You can get a copy of the Compute API WADL files at
https://github.com/openstack/compute-api/tree/master/openstack-compute-api-1.1/src
Anne
On Mon, Nov 14, 2011 at 2:21 PM, Rupak Ganguly rup...@gmail.com wrote:
Is the WADL for Nova and or its extensions available somewhere to look
Hi,
Just a friendly reminder that the first team meeting of the Nova EC2
API is tomorrow at 15:00 UTC on #openstack-meeting. The agenda is the
following:
1. Introduction
2. Testing
3. Bug work flow.
Regards
chuck
___
Mailing list:
The core API WADL is here:
https://github.com/openstack/compute-api/blob/master/openstack-compute-api-1.1/src/os-compute-1.1.wadl
Keystone also has a number of WADLs here:
https://github.com/openstack/keystone/tree/master/keystone/content
-jOrGe W.
On Nov 14, 2011, at 2:21 PM, Rupak Ganguly
I am working with OpenStack through the published API. (i.e. I am a client of the OpenStack API, not one implementing OpenStack internals). I hope that my questions will not be out-of-place on this mailing list and beg your indulgence (and correction) if they are.The current developer
Hi Scott -
You're in fact correct, though I'm puzzled as to how the OpenStack
documents are missing the Container chapter.
If you need quick info, you can refer to Cloud Files API reference info:
http://docs.rackspace.com/files/api/v1/cf-devguide/content/Create_Container-d1e1694.htmlyou'll
see
Woops, the chapter isn't missing, nor is the information. Scott, you'll
find it in
http://docs.openstack.org/api/openstack-object-storage/1.0/content/create-container.html-
you can assign metadata when you create the container.
I'll let one of the Swift devs answer about the ability to update
Anne,Thank you for your help, and you're correct, that is the case I am pursuing.In both sets of documentsit is clear to me that one can add metadata to a Containerwhen it is created. However, the documentation does not seem to mention anything aboutchangingthe metadata on a Containerafterit has
Hi Anne/Jorge,
Thanks a lot for the links.
Thanks,
Rupak Ganguly
Ph: 678-648-7434
On Mon, Nov 14, 2011 at 3:50 PM, Jorge Williams
jorge.willi...@rackspace.com wrote:
The core API WADL is here:
Updating existing container metadata with a POST is entirely supported and
intended behavior. (The same also applies to adding/updating metadata on an
account.)
--John
On Nov 14, 2011, at 8:10 PM, easco wrote:
Anne,
Thank you for your help, and you're correct, that is the case I am
John Dickinson wrote:
Updating existing container metadata with a POST is entirely supported and
intended behavior. (The same also applies to adding/updating metadata on an
account.)
Having read those exact sequences recently to determine some implications of
something I was
24 matches
Mail list logo
