The Craton fleet management midcycle meetup will be held in New York City,
August 23-26, using the following two events to provide structure/meeting
support:
- OpenStack East - developer-focused discussion on Craton core, along
with further development of integration points;
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,
sn't get merged.
>
> On Wed, May 25, 2016 at 10:27 AM, Jim Baker <jim.ba...@python.org> wrote:
>
>> 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
w 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 <jim.ba...@python.org> wrote:
>
>> On Tue, May 24, 2016 at 6:36
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
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