Re: [Openstack] Moving code hosting to GitHub

Hi Soren, On 04/22/2011 08:17 PM, Soren Hansen wrote: >> I wasn't discussing rebasing and hiding trials and errors or even >> rebasing, but cherry-picking things in a branch that we see fits, and >> are ready for a merge. > > It may not be completely obvious on the surface, but those are > essent

[Openstack] Atlas - Load Balancing Open Source Project

Stackers, I'm excited to tell the OpenStack community that the Atlas team within Rackspace is open sourcing our load balancing service. Next week we will be proposing that this project be recognized as an affiliated OpenStack project in incubation status. The Rackspace Cloud has been operating t

Re: [Openstack] Thinking about Openstack Volume API

To promote consistency across OpenStack APIs, I suggest we follow the same model as in OS compute. That is, have a high level entity called /flavors. One can query flavors to determine what types of volumes are available (based on sla, performance tiers, whatever) then pass in the flavor ID du

Re: [Openstack] Thinking about Openstack Volume API

Hey Vish, Yes, we have been thinking about that a bit. The current idea is to have volume types, and depending on the type, it would expect a certain amount of data for that type. The scheduler would then map that type and corresponding data to provision the right type of storage. -- Chuck On

Re: [Openstack] Thinking about Openstack Volume API

This all seems reasonable to me. Do you have a concept of how you will expose different SLAs within the deployment. Is it metadata on the volume that and handled by the scheduler? Or will different SLAs be at separate endpoints? In other words am i creating a volume with a PUT /provider.com/

[Openstack] Thinking about Openstack Volume API

One of the first steps needed to help decouple volumes from Nova, is to define what the Openstack Volume API should look like. I would like to start by discussing the main api endpoints, and discussing the interaction of compute attaching/detaching from volumes. All of the following endpoints wil

Re: [Openstack] Unconference forum at the Design summit

On 4/20/11 3:13 AM, "Thierry Carrez" wrote: > >Depending on the available rooms, we'll have one or more rooms dedicated >to this "unconference forum". This one will be directly organized by the >participants, by placing their session name on a big whiteboard with >empty slots waiting to be fill

Re: [Openstack] Announcing Project RedDwarf - Database as a Service

Sounds good! We can sync up after during and after the session. See you there. Thanks, Daniel From: Sebastian Stadil mailto:sebast...@scalr.com>> Date: Thu, 21 Apr 2011 23:05:47 -0700 To: Jesse Andrews mailto:anotherje...@gmail.com>> Cc: "openstack@lists.launchpad.net

Re: [Openstack] Moving code hosting to GitHub

2011/4/22 FUJITA Tomonori : >> I find the rebasing/cherry-picking practice even worse in the Linux >> kernel context due to the patch tagging used there. If I add a >> "Signed-off-by: Soren Hansen" to a patch and someone cherry picks that >> patch or moves it around as part of a rebase, my patch st

Re: [Openstack] Moving code hosting to GitHub

2011/4/22 Thomas Goirand : > On 04/22/2011 05:41 AM, Soren Hansen wrote: >> 2011/4/21 Thomas Goirand : >>> On 04/19/2011 05:55 AM, Soren Hansen wrote: 2011/4/18 Thomas Goirand : > Can't you just pull each individual patches that you feel ok with?  Is > it simply not technically possibl

[Openstack] help

Good evening all, I am an engineering student. i have poject of end of study, I want to work on"the implementation of a solution of videoconferance based on cloud computing'. I USE THE openstack for it. what you see, it's easy? . if anyone here has already done work on this type of subject.pleas

Re: [Openstack] Moving code hosting to GitHub

On Fri, Apr 22, 2011 at 4:11 PM, Thomas Goirand wrote: > > git checkout -b new-soren-branch > > This is pretty instant. Now do: > > bzr branch trunk new-soren-branch > > and wait for all files to copy ... So, bzr had a design concept at the start that folk should start in one dir and grow - like