[Openstack] about openstackx

hi Is there anyone have some doc of openstack? thanks :) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp

[Openstack] Some confusedness about network between host and vm

My environment: public ip internal ip(br100) netmaskgateway controller: 10.11.3.62 10.200.200.2 255.255.255.010.11.3.1 node: 10.11.3.63 10.200.200.3 255.255.255.010.11.3.1 I used

Re: [Openstack] OpenStack API v1.0 Removal from Nova

You should be able to continue to use novaclient with v1.0 in Diablo. Deploying Essex will require you to transition off of v1.0. Brian Waldon On Oct 12, 2011, at 5:10 PM, Venkatesan, Ravikumar wrote: > Some of us at hp still use OS Nova Client V1.0 as nova boot command is not > working with V

Re: [Openstack] OpenStack API Versioning Conventions

On 13/10/2011, at 3:15 AM, Bryan Taylor wrote: > On 10/11/2011 10:28 AM, George Reese wrote: >> It's wildly inappropriate to equate a thing with its representation. > > Unless the thing is itself a representation, yes. A resource can be ANYTHING: > a server, a database record about a server, a

Re: [Openstack] OpenStack Academic Alliance|Circle|Initiative #unconference

Cool. I will put in a few IaaS/PaaS papers I read recently. 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, October 12, 2011 5:07 PM To: o

Re: [Openstack] OpenStack Academic Alliance|Circle|Initiative#unconference

Hi It’s a great idea. Will help infuse fresh ideas. I would be very interested in helping out in the co-ordination. More thoughts inline > -Original Message- > From: openstack-bounces+dedutta=cisco@lists.launchpad.net > [mailto:openstack-bounces+dedutta=cisco@lists.launchpad.n

Re: [Openstack] OpenStack API Versioning Conventions

On 12/10/2011, at 6:10 PM, Bryan Taylor wrote: > On 10/11/2011 09:02 PM, Mark Nottingham wrote: >> While we're talking about versions -- I see that the 1.1 docs allow both URI >> and media type versioning. That makes me pretty uncomfortable, for a few >> reasons: >> >> * Having two ways to do

Re: [Openstack] OpenStack API Versioning Conventions

It's true that HTTP assigns no meaning to the extension, but HTTP leaves it to the server to decide the meaning of its own resources and their location within its URI structure. The filename extension meme is extremely common for variant resources. We adopt these conventions only so that that o

Re: [Openstack] OpenStack Academic Alliance|Circle|Initiative #unconference

On Tue, 2011-10-11 at 09:04 -0700, Stefano Maffulli wrote: > a group of people interested in academia met in Boston during the > unconference. I was there to take notes and facilitate this community > run initiative. Here is what we agreed so far. I'm sharing it on the > list to gather more ideas.

[Openstack] Nova Security and Upgrades Sessions

I added etherpads for the Nova Upgrades and Nova Security sessions at the Design Summit to EssexSummitEtherpads. The etherpads are: * nova-upgrades and * nova-security

Re: [Openstack] OpenStack API v1.0 Removal from Nova

Okay, looks like the consensus is to remove it. I do want to wait until the Ruby bindings are updated to use v1.1 as SmokeStack and one of our VPC jobs depend on it. Once that happens, I'll send another email to the list. Waldon On Oct 12, 2011, at 4:42 PM, Vishvananda Ishaya wrote: > I think

Re: [Openstack] OpenStack API v1.0 Removal from Nova

Some of us at hp still use OS Nova Client V1.0 as nova boot command is not working with V1.1. Not sure if this issue is fixed in Diablo final. Regards, Ravi ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net

Re: [Openstack] OpenStack API v1.0 Removal from Nova

I think the arguments for removing 1.0 are sound. Lets nuke it! Vish On Oct 12, 2011, at 7:39 AM, Gabe Westmaas wrote: > On 10/12/11 9:22 AM, "Jay Pipes" wrote: > >> On Wed, Oct 12, 2011 at 8:13 AM, Gabe Westmaas >> wrote: >>> I definitely get why developers working on the code base are in

Re: [Openstack] [QA] openstack-integration-tests

Thanks Jay I got it. -Nachi 2011/10/12 Jay Pipes : > Sorry for top posting... At a conference and typing from my phone... > > The openstack-qa-core group should be for core code committers to the > openstack-integrated-tests project. The fixes team is the one responsible > for the stable branches

[Openstack] Keystone and euca-tools

Using "devstack" (thank you!) made it easy to see how the keystone/nova integration was supposed to work and how to use nova client to create vms, etc. In this case the old method of using nova-manage to create users and then zipping up credentials to use with euca tools is not possible. Is the

Re: [Openstack] [QA] openstack-integration-tests

Jim++ #I suppose the scope of openstack-qa-core and fixes are very similar. 2011/10/12 James E. Blair : > Gabe Westmaas writes: > >> First, there was widespread agreement that in order for an integration >> suite to be run in the openstack jenkins, it should be included in the >> community githu

Re: [Openstack] [QA] openstack-integration-tests

Sorry for top posting... At a conference and typing from my phone... The openstack-qa-core group should be for core code committers to the openstack-integrated-tests project. The fixes team is the one responsible for the stable branches.. -jay On Oct 12, 2011 4:13 PM, "Nati Ueno" wrote: > Jim++

Re: [Openstack] OpenStack API Versioning Conventions

The extension has nothing to do with representation in HTTP. It's the content type (in the headers). Sent from my iPhone On Oct 12, 2011, at 17:15, Bryan Taylor wrote: > On 10/11/2011 10:28 AM, George Reese wrote: >> It's wildly inappropriate to equate a thing with its representation. > > Un

[Openstack] OpenStack at Ubuntu Developer Summit

Hello folks, given the strong ties between OpenStack community and Ubuntu's, I'd like to remind every OpenStack developer to go to the upcoming Ubuntu Developer Summit. Especially for the PTLs, it would be a very informative event with the Ubuntu Server track as the main attraction. The UDS is al

Re: [Openstack] [QA] openstack-integration-tests

Gabe Westmaas writes: > First, there was widespread agreement that in order for an integration > suite to be run in the openstack jenkins, it should be included in the > community github repository. Hi, During the meeting today, folks asked about what the core group is for the openstack-integra

Re: [Openstack] [RFC] Stable branch

Mark McLoughlin writes: > Hey, > > I've posted a proposal for how the stable branch could work here: > > http://wiki.openstack.org/StableBranch > > and a proposed diablo branch for nova: > > http://github.com/markmc/nova/tree/diablo > > The wiki page seems to be 404 for folks for some bizarre

Re: [Openstack] OpenStack API Versioning Conventions

George Reese wrote: > HTTP methods are well defined and the system should behave in accordance with those definitions. Otherwise, even saying the word REST is a joke. Is your point that because OpenStack APIs should be REST complaint that there would never be a "V2" on a Get operation? That is

[Openstack] [RFC] Stable branch

Hey, I've posted a proposal for how the stable branch could work here: http://wiki.openstack.org/StableBranch and a proposed diablo branch for nova: http://github.com/markmc/nova/tree/diablo The wiki page seems to be 404 for folks for some bizarre reason, but you can get to it from: wik

Re: [Openstack] OpenStack API Versioning Conventions

On 10/11/2011 10:28 AM, George Reese wrote: > It's wildly inappropriate to equate a thing with its representation. Unless the thing is itself a representation, yes. A resource can be ANYTHING: a server, a database record about a server, a car, a rock, the concept of love, the act of smiling, or

Re: [Openstack] openstack storage comparison with extreemfs

Hi Sudhakar - I'm not terribly familiar with xtreemFS, but glancing at their website, it looks like it's replicated block-volume mechanism not unlink gluster or ceph. There is no plugin or back-end that takes the Nova block volume components and uses this - if it supports an iSCSI interface to

Re: [Openstack] Guidelines for OpenStack APIs

On 10/11/2011 09:08 AM, Mark McLoughlin wrote: Btw, which APIs are we talking about here? Just compute and storage. Or image and identity too? I think this should be much broader and include any API contributed to the OpenStack banner, including those in the OpenStack Satellite. This email m

Re: [Openstack] swift and rsync

Hi Fabrice, The design of Swift has always assumed that the backend services are running on a secured, private network. If this is not going to be the case, or you would like to provide more security on that network, a lot more work needs to be done than just rsync. That said, I don't think it

Re: [Openstack] OpenStack API v1.0 Removal from Nova

On 10/12/11 9:22 AM, "Jay Pipes" wrote: >On Wed, Oct 12, 2011 at 8:13 AM, Gabe Westmaas > wrote: >> I definitely get why developers working on the code base are in favor of >> this, especially for reasons 3 and 4 below. However, there are a couple >> of reasons that it might make sense to keep i

Re: [Openstack] OpenStack API v1.0 Removal from Nova

From my perspective, the 1.0 API was unusable. Prior to 1.1, everyone I knew of was universally using the EC2 API. If I thought for a second someone was actually using the 1.0 API, I would not have been silent on this thread given my "support forever" stance :) -George On Oct 12, 2011, at 1:13

Re: [Openstack] OpenStack API v1.0 Removal from Nova

On Wed, Oct 12, 2011 at 8:13 AM, Gabe Westmaas wrote: > I definitely get why developers working on the code base are in favor of > this, especially for reasons 3 and 4 below.  However, there are a couple > of reasons that it might make sense to keep it, and I'd really like to > hear from a differe

[Openstack] FLOSSK in Kosovo -- OpenStack speakers wanted

Hey Stackers, There is a cool FLOSS conference in Kosovo coming up on November 12th -- Software Freedom Kosova 2011. If you're interested in speaking there, feel free to check out this blog post: http://www.flossk.org/en/blog/sfk11 and contact i...@flossk.org. Cheers! -jay ___

Re: [Openstack] [Nova] MySQL drivers in DB

On Wed, Oct 12, 2011 at 7:54 AM, Gabe Westmaas wrote: > +1 on modifying it in your environment,  this seems outside the scope of > migrations, though perhaps listed as a "best practice" for the deployment > process. +1 > Similarly, I have been trying to decide what makes sense for indexes. > Rig

Re: [Openstack] glance-api errors and stop

This may indeed be a Django-related problem... I tried investigating it a bit (known bug), but that investigation didn't get that far :( https://bugs.launchpad.net/glance/+bug/862664 Please let's continue this discussion on the bug report above. Thanks! -jay 2011/10/12 mao weijie : > Does anyon

Re: [Openstack] glance-api errors and stop

Does anyone meet this problem? I think it is Django(python) problem. more log: 2011-10-12 06:22:01DEBUG [eventlet.wsgi.server] 10.200.200.2 - - [12/Oct/2011 06:22:01] "GET /v1/images/4 HTTP/1.1" 200 66241 0.109968 2011-10-12 06:22:03DEBUG [glance.api.middleware.version_negotiation] Pro

Re: [Openstack] OpenStack API v1.0 Removal from Nova

I definitely get why developers working on the code base are in favor of this, especially for reasons 3 and 4 below. However, there are a couple of reasons that it might make sense to keep it, and I'd really like to hear from a different demographic, if at all possible. First, I'd like to hear fr

Re: [Openstack] [Nova] MySQL drivers in DB

I'm not that interested in engines - this does look out of scope, since forcing something here might prevent people from running mysql cluster (ndb engine is required then). I was wondering about indexes though - I was going to submit a patch for it in the future actually. Since big, db-stoppin

Re: [Openstack] [Nova] MySQL drivers in DB

+1 on modifying it in your environment, this seems outside the scope of migrations, though perhaps listed as a "best practice" for the deployment process. Similarly, I have been trying to decide what makes sense for indexes. Right now it would be a bad idea to run nova without adding some indexes

Re: [Openstack] OpenStack API Versioning Conventions

On Oct 12, 2011, at 11:23 AM, Soren Hansen wrote: > 2011/10/11 George Reese : >> It's wildly inappropriate to equate a thing with its representation. > > I didn't say I was right in doing so :) > > It's a discussion that gets philosophical rather quickly: Should we > consider a URI to be a refe

Re: [Openstack] OpenStack API Versioning Conventions

On Oct 12, 2011, at 11:26 AM, Soren Hansen wrote: > 2011/10/11 George Reese : >> See EC2 for someone doing it damn well. I've never had to write new code to >> talk to them unless I want to take advantage of new functionality. > > Now I'm confused. EC2 includes the API version in the URI, but I

[Openstack] swift and rsync

swift uses rsync for some synchronization tasks. But for what I can see, it mades a very raw usage of it : In db_replicator.py : def _rsync_file(self, db_file, remote_file, whole_file=True): ... popen_args = ['rsync', '--quiet', '--no-motd', '--timeout=%s'

Re: [Openstack] OpenStack API Versioning Conventions

2011/10/11 George Reese : > See EC2 for someone doing it damn well. I've never had to write new code to > talk to them unless I want to take advantage of new functionality. Now I'm confused. EC2 includes the API version in the URI, but I thought you were opposed to that? -- Soren Hansen        

Re: [Openstack] OpenStack API Versioning Conventions

2011/10/11 George Reese : > It's wildly inappropriate to equate a thing with its representation. I didn't say I was right in doing so :) It's a discussion that gets philosophical rather quickly: Should we consider a URI to be a reference to a thing or a reference to a representation of a thing?

[Openstack] openstack storage comparison with extreemfs

Hi, can anyone tell me that if we can implment openstack stroage as extreemfs. Regards Sudhakar ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :

Re: [Openstack] [OPENSTACK] Does diablo support lvm block devices instead files for VMs?

It supports iSCSI volumes which employ the use of LVM, http://docs.openstack.org/diablo/openstack-compute/admin/content/managing-volumes.html. The template file you reference is not the full picture. When you mount a volume a new snippet of XML is generated and passed to libvirt. The XML would

Re: [Openstack] OpenStack API Versioning Conventions

On 10/11/2011 09:02 PM, Mark Nottingham wrote: While we're talking about versions -- I see that the 1.1 docs allow both URI and media type versioning. That makes me pretty uncomfortable, for a few reasons: * Having two ways to do it is duplication of effort / more opportunit