specific version
would almost certainly cause issues.
Dan
- Original Message -
> From: "James Slagle"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Wednesday, January 8, 2014 10:03:39 AM
> Subject: Re: [openstack-dev] [T
We're in agreement. What little entry there might be in a system of such
a small size would be entirely manageable by a single administrator...
I care about that deployment, deeply, as that is how things like OpenStack
take root in IT departments.. with somebody playing around. However, what
I car
ll tools though,
there isn't one "works for all cases best" tool.
I hope this use case helps.
Thanks,
Kevin
From: Clint Byrum [cl...@fewbar.com]
Sent: Wednesday, January 08, 2014 8:36 AM
To: openstack-dev
Subject: Re: [openstack-dev] [Triple
Excerpts from Jan Provaznik's message of 2014-01-08 03:00:19 -0800:
> On 01/07/2014 09:01 PM, James Slagle wrote:
> > Hi,
> >
> > I'd like to discuss some possible ways we could install the OpenStack
> > components from packages in tripleo-image-elements. As most folks are
> > probably aware, ther
Excerpts from Jay Dobies's message of 2014-01-08 08:09:51 -0800:
> There were so many places in this thread that I wanted to jump in on as
> I caught up, it makes sense to just summarize things in once place
> instead of a half dozen quoted replies.
>
> I agree with the sentiments about flexibil
Excerpts from James Slagle's message of 2014-01-08 07:03:39 -0800:
> On Tue, Jan 7, 2014 at 11:20 PM, Robert Collins
> wrote:
> > On 8 January 2014 12:18, James Slagle wrote:
> >> Sure, the crux of the problem was likely that versions in the distro
> >> were too old and they needed to be updated.
Excerpts from Derek Higgins's message of 2014-01-08 02:11:09 -0800:
> On 08/01/14 05:07, Clint Byrum wrote:
> > Excerpts from Fox, Kevin M's message of 2014-01-07 16:27:35 -0800:
> >> Another piece to the conversation I think is update philosophy. If
> >> you are always going to require a new image
There were so many places in this thread that I wanted to jump in on as
I caught up, it makes sense to just summarize things in once place
instead of a half dozen quoted replies.
I agree with the sentiments about flexibility. Regardless of my personal
preference on source v. packages, it's bee
On Tue, Jan 7, 2014 at 11:20 PM, Robert Collins
wrote:
> On 8 January 2014 12:18, James Slagle wrote:
>> Sure, the crux of the problem was likely that versions in the distro
>> were too old and they needed to be updated. But unless we take on
>> building the whole OS from source/git/whatever eve
On 01/07/2014 09:01 PM, James Slagle wrote:
Hi,
I'd like to discuss some possible ways we could install the OpenStack
components from packages in tripleo-image-elements. As most folks are
probably aware, there is a "fork" of tripleo-image-elements called
tripleo-puppet-elements which does insta
On 08/01/14 05:07, Clint Byrum wrote:
> Excerpts from Fox, Kevin M's message of 2014-01-07 16:27:35 -0800:
>> Another piece to the conversation I think is update philosophy. If
>> you are always going to require a new image and no customization after
>> build ever, ever, the messiness that source u
Excerpts from Jay Pipes's message of 2014-01-07 21:26:44 -0800:
> On Wed, 2014-01-08 at 17:20 +1300, Robert Collins wrote:
> > On 8 January 2014 12:18, James Slagle wrote:
> > > Sure, the crux of the problem was likely that versions in the distro
> > > were too old and they needed to be updated.
On Wed, 2014-01-08 at 17:20 +1300, Robert Collins wrote:
> On 8 January 2014 12:18, James Slagle wrote:
> > Sure, the crux of the problem was likely that versions in the distro
> > were too old and they needed to be updated. But unless we take on
> > building the whole OS from source/git/whatever
Excerpts from Fox, Kevin M's message of 2014-01-07 16:27:35 -0800:
> Another piece to the conversation I think is update philosophy. If
> you are always going to require a new image and no customization after
> build ever, ever, the messiness that source usually cause in the file
> system image rea
On 8 January 2014 12:18, James Slagle wrote:
> I'm reminded of when I first started looking at TripleO there were a
> few issues with installing from git (I'll say that from now on :)
> related to all the python distribute -> setuptools migration. Things
> like if you're base cloud image had the
On 8 January 2014 09:23, Clint Byrum wrote:
> What would be the benefit of using packages?
- Defense in depth - tests at the package build time + tests of the image.
- Enumeration of installed software using the admins expected tooling
(dpkg / rpm etc)
- Familiarity
> We've specifically avoided
On 8 January 2014 12:26, Fox, Kevin M wrote:
> One of the major features using a distro over upstream gives is integration.
> rhel6 behaves differently then ubuntu 13.10. Sometimes it takes a while to
> fix upstream for a given distro, and even then it may not even be accepted
> because "the dis
Excerpts from James Slagle's message of 2014-01-07 15:18:00 -0800:
> On Tue, Jan 7, 2014 at 6:04 PM, Clint Byrum wrote:
> > Excerpts from Chris Jones's message of 2014-01-07 14:43:31 -0800:
> >> Hi
> >>
> >> > On 7 Jan 2014, at 22:18, Clint Byrum wrote:
> >> > Packages do the opposite,
> >> > and
On Tue, Jan 7, 2014 at 6:45 PM, Clint Byrum wrote:
> Excerpts from James Slagle's message of 2014-01-07 15:03:33 -0800:
>> On Tue, Jan 7, 2014 at 5:18 PM, Clint Byrum wrote:
>> > Excerpts from James Slagle's message of 2014-01-07 12:53:57 -0800:
>> >> On Tue, Jan 7, 2014 at 3:23 PM, Clint Byrum
ge questions)
Subject: Re: [openstack-dev] [TripleO] Installing from packages in
tripleo-image-elements
On Tue, Jan 7, 2014 at 6:12 PM, Clint Byrum wrote:
> Excerpts from Fox, Kevin M's message of 2014-01-07 13:11:13 -0800:
>> I was going to stay silent on this one, but since you aske
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Tuesday, January 7, 2014 3:23:24 PM
> Subject: Re: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> What would be the benefit o
Hi
> On 7 Jan 2014, at 23:04, Clint Byrum wrote:
>
> My question still stands, what are the real advantages? So far the only
> one that matters to me is "makes it easier for people to think about
> using it."
If I were to put on my former sysadmin hat, I would always strongly prefer to
use pac
- Original Message -
> From: "James Slagle"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, January 7, 2014 3:53:57 PM
> Subject: Re: [openstack-dev] [TripleO] Installing from packages in
> tripleo-imag
- Original Message -
> From: "James Slagle"
> To: "OpenStack Development Mailing List"
> Sent: Tuesday, January 7, 2014 3:01:07 PM
> Subject: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> Hi,
>
On Tue, Jan 7, 2014 at 6:12 PM, Clint Byrum wrote:
> Excerpts from Fox, Kevin M's message of 2014-01-07 13:11:13 -0800:
>> I was going to stay silent on this one, but since you asked...
>>
>> /me puts his customer hat on
>>
>> We source OpenStack from RDO for the packages and additional integratio
Excerpts from James Slagle's message of 2014-01-07 15:03:33 -0800:
> On Tue, Jan 7, 2014 at 5:18 PM, Clint Byrum wrote:
> > Excerpts from James Slagle's message of 2014-01-07 12:53:57 -0800:
> >> On Tue, Jan 7, 2014 at 3:23 PM, Clint Byrum wrote:
> >> > What would be the benefit of using packages
__
From: Clint Byrum [cl...@fewbar.com]
Sent: Tuesday, January 07, 2014 3:04 PM
To: openstack-dev
Subject: Re: [openstack-dev] [TripleO] Installing from packages in
tripleo-image-elements
Excerpts from Chris Jones's message of 2014-01-07 14:43:31 -0800:
> Hi
>
> &
On Tue, Jan 7, 2014 at 6:04 PM, Clint Byrum wrote:
> Excerpts from Chris Jones's message of 2014-01-07 14:43:31 -0800:
>> Hi
>>
>> > On 7 Jan 2014, at 22:18, Clint Byrum wrote:
>> > Packages do the opposite,
>> > and encourage entropy by promising to try and update software
>>
>> Building with pa
Excerpts from Fox, Kevin M's message of 2014-01-07 13:11:13 -0800:
> I was going to stay silent on this one, but since you asked...
>
> /me puts his customer hat on
>
> We source OpenStack from RDO for the packages and additional integration
> testing that comes from the project instead of using
Excerpts from Chris Jones's message of 2014-01-07 14:43:31 -0800:
> Hi
>
> > On 7 Jan 2014, at 22:18, Clint Byrum wrote:
> > Packages do the opposite,
> > and encourage entropy by promising to try and update software
>
> Building with packages doesn't require updating running systems with packa
On Tue, Jan 7, 2014 at 5:18 PM, Clint Byrum wrote:
> Excerpts from James Slagle's message of 2014-01-07 12:53:57 -0800:
>> On Tue, Jan 7, 2014 at 3:23 PM, Clint Byrum wrote:
>> > What would be the benefit of using packages?
>>
>> We're building images on top of different distributions of Linux.
>
Hi
> On 7 Jan 2014, at 22:18, Clint Byrum wrote:
> Packages do the opposite,
> and encourage entropy by promising to try and update software
Building with packages doesn't require updating running systems with packages
and more than building with git requires updating running systems with git
Hi
> On 7 Jan 2014, at 21:17, James Slagle wrote:
>
> Could you expand on this a bit? I'm not sure what inconsistency
> you're referring to.
That multiple repos work, but the docs don't say so, and the DIB_REPO foo
doesn't support multiple repos.
> I wonder if we could have a global build o
Excerpts from James Slagle's message of 2014-01-07 12:53:57 -0800:
> On Tue, Jan 7, 2014 at 3:23 PM, Clint Byrum wrote:
> > What would be the benefit of using packages?
>
> We're building images on top of different distributions of Linux.
> Those distributions themselves offer packaged and suppor
On Tue, Jan 7, 2014 at 3:48 PM, Chris Jones wrote:
> Hi
>
> Assuming we want to do this, but not necessarily agreeing that we do want to,
> I would suggest:
>
> 1) I think it would be nice if we could avoid separate dpkg/rpm types by
> having a package type and reusing the package map facility.
ubject: Re: [openstack-dev] [TripleO] Installing from packages in
tripleo-image-elements
Hi
Assuming we want to do this, but not necessarily agreeing that we do want to, I
would suggest:
1) I think it would be nice if we could avoid separate dpkg/rpm types by having
a package type and r
gt;
>> From: James Slagle [james.sla...@gmail.com]
>> Sent: Tuesday, January 07, 2014 12:01 PM
>> To: OpenStack Development Mailing List
>> Subject: [openstack-dev] [TripleO] Installing from packages in
>> tripleo-image-elements
>
On Tue, Jan 7, 2014 at 3:23 PM, Clint Byrum wrote:
> What would be the benefit of using packages?
We're building images on top of different distributions of Linux.
Those distributions themselves offer packaged and supported OpenStack
components. So, one benefit is that you'd be using what's "ble
Hi
Assuming we want to do this, but not necessarily agreeing that we do want to, I
would suggest:
1) I think it would be nice if we could avoid separate dpkg/rpm types by having
a package type and reusing the package map facility.
2) Clear up the source-repositories inconsistency by making it
Hi
My guess for the easiest answer to that: distro vendor support.
Cheers,
--
Chris Jones
> On 7 Jan 2014, at 20:23, Clint Byrum wrote:
>
> What would be the benefit of using packages?
>
> We've specifically avoided packages because they complect[1] configuration
> and system state management
From: James Slagle [james.sla...@gmail.com]
> Sent: Tuesday, January 07, 2014 12:01 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [TripleO] Installing from packages in
> tripleo-image-elements
>
> Hi,
>
> I'd like to discuss some possible ways we
What would be the benefit of using packages?
We've specifically avoided packages because they complect[1] configuration
and system state management with software delivery. The recent friction
we've seen with MySQL is an example where the packages are not actually
helping us, they're hurting us bec
[james.sla...@gmail.com]
Sent: Tuesday, January 07, 2014 12:01 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [TripleO] Installing from packages in
tripleo-image-elements
Hi,
I'd like to discuss some possible ways we could install the OpenStack
components from packag
Hi,
I'd like to discuss some possible ways we could install the OpenStack
components from packages in tripleo-image-elements. As most folks are
probably aware, there is a "fork" of tripleo-image-elements called
tripleo-puppet-elements which does install using packages, but it does
so using Puppet
44 matches
Mail list logo
