On Wed, May 25, 2016 at 12:47 PM, Tim Bell wrote:
> Slight concern on how to deploy on a RHEL system base as software
> collections are non-trivial.
>
But also worth keeping in mind, Craton and its dependencies (most
significantly, MySQL or PostgreSQL, + Taskflow dependencies, including
ZooKeepe
I can make the request a move rather than copy. Then anyone landing at the
old repo get redirected to the new.
On Wed, May 25, 2016 at 10:37 AM, Jim Baker wrote:
> We will want to move the main repo to OpenStack infra, with the usual
> mirror to github.com/openstack/craton. I don't think we need
We will want to move the main repo to OpenStack infra, with the usual
mirror to github.com/openstack/craton. I don't think we need to worry about
mirroring to github.com/rackerlabs/craton as well. A simple reference there
pointing to the new location should suffice.
Basically I'm just trying to ke
True, we will want to wait if we want decide to move or copy the
rackerlabs/craton repo. I can create the project patch and then pin it so
it doesn't get merged.
On Wed, May 25, 2016 at 10:27 AM, Jim Baker wrote:
> Sean, thanks for your help here, it's very much appreciated!
>
> The move then sh
Sean, thanks for your help here, it's very much appreciated!
The move then should be straightforward once we get past our first
milestone, on or around June 10; but any prep in advance sounds good.
On Wed, May 25, 2016 at 12:37 PM, sean roberts
wrote:
> Now that we have settled on the name, s
From: Jim Baker
Date: Wednesday 25 May 2016 at 00:51
To: Sam Morrison
Cc: openstack-operators
Subject: Re: [Openstack-operators] [craton] Versions of Python to support for
Craton
On Tue, May 24, 2016 at 6:36 PM, Sam Morrison
mailto:sorri...@gmail.com>> wrote:
I’m in favour of using 3
Now that we have settled on the name, setting up the project infrastructure
is straightforward. I have done this a few times and am ready to do it for
craton.
On Tue, May 24, 2016 at 3:51 PM, Jim Baker wrote:
> On Tue, May 24, 2016 at 6:36 PM, Sam Morrison wrote:
>
>> I’m in favour of using 3.5
On Tue, May 24, 2016 at 6:36 PM, Sam Morrison wrote:
> I’m in favour of using 3.5. We are in the process of moving things to
> ubuntu xenial and 3.5 is native there.
>
Thanks for the feedback!
>
> BTW when is Craton planning on getting into openstack gerrit etc?
>
The specific timeline of the
I’m in favour of using 3.5. We are in the process of moving things to ubuntu
xenial and 3.5 is native there.
BTW when is Craton planning on getting into openstack gerrit etc?
Sam
> On 25 May 2016, at 6:20 AM, Jim Baker wrote:
>
> tl;dr - any reason why Craton should support Python 2.7 for
tl;dr - any reason why Craton should support Python 2.7 for your use case?
First, some background: Craton is a fleet management tool under active
development for standing up and maintaining OpenStack clouds. It does so by
supporting inventory and audit/remediation workflows, both at scale and
bein
10 matches
Mail list logo
