Re: [Openstack] [GLANCE] Proposal: Combine the container_format and disk_format fields in 2.0 Images API

2011-12-02 Thread Soren Hansen
2011/12/1 Jay Pipes jaypi...@gmail.com: structure tar'd up. However, I think this can be more easily accomplished by consolidating the disk and container formats in the 2.0 API to just a single format field with the possible values:    ova - This indicates the data stored in Glance is an OVF

Re: [Openstack] [GLANCE] Proposal: Combine the container_format and disk_format fields in 2.0 Images API

2011-12-02 Thread Donal Lafferty
During October I noticed that Microsoft's vhdtool.exe creates VHDs that XenServer can't understand. Boy was that painful. The underlying problem is that some vhd's should be described as VM specific. Does this suggest we adopt MIME-like syntax for category specialization? E.g. in the same

Re: [Openstack] [GLANCE] Proposal: Combine the container_format and disk_format fields in 2.0 Images API

2011-12-02 Thread Soren Hansen
2011/12/2 Donal Lafferty donal.laffe...@citrix.com: During October I noticed that Microsoft's vhdtool.exe creates VHDs that XenServer can't understand.  Boy was that painful. The underlying problem is that some vhd's should be described as VM specific. Can you elaborate on this, please? I

Re: [Openstack] boot from ISO

2011-12-02 Thread Donal Lafferty
The background is that having provided a sample implementation, developers targeting libvirt would offer the same functionality. DL From: Michaël Van de Borne [mailto:michael.vandebo...@cetic.be] Sent: 01 December 2011 16:34 To: Anne Gentle Cc: Donal Lafferty; openstack@lists.launchpad.net

Re: [Openstack] [GLANCE] Proposal: Combine the container_format and disk_format fields in 2.0 Images API

2011-12-02 Thread Soren Hansen
2011/12/2 Donal Lafferty donal.laffe...@citrix.com: The key in my email was to ask whether MIME-like specialisations were appropriate either for combining characteristics of an image into a single property. E.g. container_type/image_type.  The example I provided was

[Openstack] HPC with Openstack?

2011-12-02 Thread Sandy Walsh
I've recently had inquiries about High Performance Computing (HPC) on Openstack. As opposed to the Service Provider (SP) model, HPC is interested in fast provisioning, potentially short lifetime instances with precision metrics and scheduling. Real-time vs. Eventually. Anyone planning on using

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread David Busby
May be worth looking at rightscale: http://www.rightscale.com/products/plans-pricing/grid-edition.php The article there is only and only cites EC2 usage, but their API's support Rackspace cloud which is Nova http://support.rightscale.com/12-Guides/RightScale_API Cheers David On 2 Dec 2011,

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Lorin Hochstein
As a side note, HPC means very different things to different people. In the circles I move in, HPC is interested in running compute jobs that are CPU-intensive, require large amounts of memory, and need low-latency/high-bandwidth interconnects to allow the user to break up a tightly coupled

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Oleg Gelbukh
Hello, Here at Mirantis we are working on deployment of Openstack that intended to manage HPC cluster eventually. There are few features that we are going to incorporate, and we are still researching. The general idea is to use LXC as a lightweight virtualization engine, and make use of faster

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Sandy Walsh
Good point ... thanks for the clarification. -S From: Lorin Hochstein [lo...@isi.edu] Sent: Friday, December 02, 2011 9:47 AM To: Sandy Walsh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] HPC with Openstack? As a side note, HPC means very different

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Brian Schott
You did see that Amazon hit #42 on the Top 500 supercomputing list? It is somewhat of a stunt, but the point is that access to a supercomputer is a credit-card swipe away and rentable by the hour. There was a lot of buzz at SC11 a few weeks ago. There are several HPC groups in the OpenStack

Re: [Openstack] Keystone Swift: swiftauth tenant namespace collisions?

2011-12-02 Thread Ziad Sawalha
Great. BTW, Dolph just started work on this, so we've updated the status of the blueprint. Z From: Judd Maltin openst...@newgoliath.commailto:openst...@newgoliath.com Date: Fri, 2 Dec 2011 11:27:57 -0500 To: Ziad Sawalha ziad.sawa...@rackspace.commailto:ziad.sawa...@rackspace.com Cc:

Re: [Openstack] API specifications

2011-12-02 Thread Nachi Ueno
Hi Brian Thank you for your response. How about params which is missing in docs? accessIPv4 accessIPv6 adminPass config_drive security_groups networks blob keyname availability_zone reservation_id min_count max_count 2011/12/1 Brian Waldon brian.wal...@rackspace.com: Our consoles resource is

Re: [Openstack] API specifications

2011-12-02 Thread Nachi Ueno
Hi Chris Sorry, I missed that. Would you give me url? Such as console.py, it is not in contrib directory. 2011/12/2 Christopher MacGown ch...@pistoncloud.com: Hi Nachi, At least for config_drive, it has been documented as an extension. - chris On Dec 2, 2011, at 10:07, Nachi Ueno

Re: [Openstack] API specifications

2011-12-02 Thread Nachi Ueno
Hi Gabe I got your point. However,I wanna know it is extension or not. Cheers Nati 2011/12/2 Gabe Westmaas gabe.westm...@rackspace.com: Hi Nachi, The reason for excluding those from being required in the create response is to allow us to make those creates as asynchronous as possible.

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Oliver Baltzer
As a side note, HPC means very different things to different people. In the circles I move in, HPC is interested in running compute jobs that are CPU-intensive, require large amounts of memory, and need low-latency/high-bandwidth interconnects to allow the user to break up a tightly coupled

Re: [Openstack] API specifications

2011-12-02 Thread Brian Waldon
accessIPv4 and accessIPv6 are both core instance attributes. The rest are all attributes owned by existing extensions. Keep in mind that the spec doesn't require all attributes to be returned in a POST response. Chris - I don't think config_drive is documented as an extension. This bug is

Re: [Openstack] API specifications

2011-12-02 Thread Nachi Ueno
Hi folks Anne Sorry,I remember now. I got extension docs from you. 2011/12/2 Brian Waldon brian.wal...@rackspace.com: accessIPv4 and accessIPv6 are both core instance attributes. The rest are all attributes owned by existing extensions. Keep in mind that the spec doesn't require all

Re: [Openstack] API specifications

2011-12-02 Thread Daryl Walleck
Hi Gabe, I think what Nachi is saying is that these parameters can be taken in a create request, but are not documented (I say this also because I've seen this in novaclient as well). I know they're not required, but I'm curious what their purpose is. Daryl On Dec 2, 2011, at 12:16 PM, Gabe

[Openstack] OpenStack Community Newsletter –December 1, 2011

2011-12-02 Thread Stefano Maffulli
OpenStack Community Newsletter –December 1, 2011 HIGHLIGHTS * Help building the list of events worldwide where OpenStack should be represented http://etherpad.openstack.org/OpenStackEvents2012 * Zadara Storage won the Innovation Showdown Contest at Cloudbeat

Re: [Openstack] Cloud Computing StackExchange site proposal

2011-12-02 Thread Stefano Maffulli
On Mon, 2011-11-28 at 08:17 -0800, Stefano Maffulli wrote: Leaving aside naming the tools, what would be the most important features to have? Here is the list of requirements we gathered: * good search engine * ability to promote question and best answer to FAQ * good looking and nice to use

Re: [Openstack] HPC with Openstack?

2011-12-02 Thread Leandro Reox
An HPC way of usage for.openstack at.mercadolibre is for example to run integration and regresions test on productios pre and post deploy too. So Jenkins servers are shooted in a minute to support the tests load and then they destroy themselves. On Dec 2, 2011 3:55 PM, Oliver Baltzer