Has anyone surveyed those subscribed to openstack-operators@lists.openstack.org
list for usage? While imperfect, at least it would be asking the
constituency that might be most affected. You might also consider asking
whether they would prefer JSON or XML, regardless of what they use today.I agre
+1Cheers,Christopher FerrisIBM Distinguished Engineer, CTO Industry and Cloud StandardsMember, IBM Academy of TechnologyIBM Software Group, Standards Strategyemail: chris...@us.ibm.comTwitter: christo4ferrisphone: +1 508 234 2986-openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote:
Gabriel Hurley wrote:>As a rule of thumb, we need to start doing proper deprecation on all>public interfaces, whether that's a CLI, client method signatures,>APIs, etc. It's a little late for this on the old vs. new glance>client/CLI (unless Brian feels the work can be reasonably done to>make them
Thierry Carrez wrote:[snip]>>> As such IMHO we should leave it as it is.>>Especially since Launchpad-based MLs don't give us the option to>change>that behavior anyway :)LMAO! TouchéCheers,Christopher FerrisIBM Distinguished Engineer, CTO Industry and Cloud StandardsMember, IBM Academy of Technology
Speaking of the User Committee as proposed in the draft governance docs, I
can
certainly see value in having the committee chair chosen by the board.
However, as
currently proposed, there is a convoluted process for appointing the
representatives
of the committee. Frankly, if you want to give a vo
Sent from my iPad
On Jul 13, 2012, at 12:41 AM, "Blake Yeager"
wrote:
>
>
> I am excited to see such passion from the community but we need to make
sure that passion is directed in a constructive manner.
+1
Chris___
Mailing list: https://launchpa
This is exactly the sort of interaction we need between the two perspectives of
the OpenStack community.
Thanks
Chris
Sent from my iPad
On Jul 12, 2012, at 11:20 PM, "Joe Topjian" wrote:
> Hello,
>
> I'm not an OpenStack developer nor any type of developer. I am, however,
> heavily involve
+1 to Vish's proposal
I'd go a step further and suggest adopt this model for such changes going
forward.
Chris
Sent from my iPad
On Jul 12, 2012, at 5:40 PM, "Vishvananda Ishaya"
wrote:
> On Jul 12, 2012, at 2:36 PM, David Mortman wrote:
>
> > On Thu, Jul 12, 2012 at 3:38 PM, Vishvananda Is
This level of response is unnecessary.
That said, the perspectives which influenced the decision seemed somewhat
weighted to the development community. I could be wrong, but I did not see much
input from the operations community as to the impact.
Clearly, going forward, we want to be more deli
Just to be clear, I was +1 ing Sean's point that we should get sme
experience behind this before pulling the plug.
Chris
Sent from my iPad
On Jul 11, 2012, at 3:02 PM, "Sean Dague"
wrote:
> Before we completely pile on option 1, can we get devstack changed to
> run this way? I think the amoun
+1
Chris
Sent from my iPad
On Jul 11, 2012, at 3:02 PM, "Sean Dague"
wrote:
> Before we completely pile on option 1, can we get devstack changed to
> run this way? I think the amount of pain / ease that transition is for
> users and the OpenStack CI team will greatly inform this decision, and
John Postlethwait wrote:
>... Also, you need to make sure you are linking DIRECTLY to the image
>itself, as if it is a redirect or any other HTTP response besides the file,
>Glance will still create an image out of it and it will seem to have worked.
>Sometimes you can even launch said instances t
-openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: -
>To: openstack@lists.launchpad.net
>From: Monty Taylor
[snip]
>So honestly, I'd say the real key is getting us closer to the point
>where openstack-common is a proper library, because all of the rest of
>the complexity
-1
Gazelle seems to carry more of the characteristics we would want (nimble,
quick). Grizzly carries rather grim connotations
of mauling, lumbering, and having a rather nasty disposition. I would not want
that in a cloud.
Also, as an adjective, grizzly means 'showing characteristics of age,
e
-openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: -
>To: "andrewbog...@gmail.com" , Andrew Bogott
>, openstack
>From: Joshua Harlow
>Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net
>Date: 07/02/2012 07:21PM
>Subject: Re: [Openstack] best practices for
+1
Chris
Sent from my iPad
On Jun 26, 2012, at 3:42 PM, "Anne Gentle" wrote:
> Sounds good to me. Mo working doc builds, mo betta.
>
> Anne Gentle
> Content Stacker
> a...@openstack.org
>
> On Tue, Jun 26, 2012 at 9:02 AM, Monty Taylor
wrote:
> > Hey guys!
> >
> > We have all of the projects
> Probably not important on a privatecloud deployment, but certainly important in the public cloud space.Actually, I'd say it is equally important in a private cloud context as public. Just because the cloud is behind a firewall does not mean it does not need to be secured as carefully as if it wer
+1 Over-reliance on WADL will only make it more challenging to gracefully evolve the APIs such that implementations can be forwards and/or backwards compatible, especially when exchanging XML based on an XSD that is not carefully crafted with proper extensibility points incorporated throughout the
+1> Ideally I'd like to see an OpenStack API feature contract of some sort... essentially a document describing the FULL > list of features, how those parameters are controlled and how they would interact, and what a project should do if > they do not implement an API feature (hopefully only for te
case-insensitive - why would 'Admin' and 'admin' be different? Sure, a role is represented by a string, but why does that string need to be case sensitive?I'd think that if you had distinct roles attributed to 'Admin' and 'admin' that that would lead to confusion.Cheers,Christopher FerrisIBM Distin
@lists.launchpad.net wrote: -To: openstack@lists.launchpad.netFrom: Stefano Maffulli Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.netDate: 06/01/2012 12:23PMSubject: Re: [Openstack] search on the mailing listOn 06/01/2012 04:21 AM, Christopher B Ferris wrote:> Could we get these links added
Could we get these links added to the splash on https://launchpad.net/openstack? I'm sure this is a rather common problem.e.g.:Mailing list - openstack@lists.launchpad.net - see https://launchpad.net/~openstack to join - searchable archives: http://www.mail-archive.com/openstack@lists.launchpad.n
+1Cheers,Christopher FerrisIBM Distinguished Engineer, CTO Industry and Cloud StandardsMember, IBM Academy of TechnologyIBM Software Group, Standards Strategyemail: chris...@us.ibm.comTwitter: christo4ferrisphone: +1 508 234 2986-openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote:
+1It is important that we distinguish between those who might contribute to the development of OpenStack, who often have advancedlanguage skills, as contrasted with those who might be asked to operate a cloud based on OpenStack. While it may be that the languageof open source development is English
24 matches
Mail list logo
