Kevin,

I really didn’t want to badmouth osad, as I think its a great piece of tech.  I 
hope you didn’t take my analysis as such.  We just have different approaches to 
solving problems.

I think admin best practices you are following.  Thanks for that clarification. 
 The battle over what a container should be I’ll leave to the container 
community to battle over ;)

To be fair to all parties involved, OSAD is real and exists today – Our plans 
for Kolla only become real by converting our specification into real working 
code.  I am highly confident this can be done in the Liberty cycle with the ~15 
developers that have come together to implement it.

Regards
-steve


From: Kevin Carter 
<kevin.car...@rackspace.com<mailto:kevin.car...@rackspace.com>>
Date: Monday, June 8, 2015 at 7:28 AM
To: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>>, Craig Tracey 
<cr...@craigtracey.com<mailto:cr...@craigtracey.com>>, James Denton 
<james.den...@rackspace.com<mailto:james.den...@rackspace.com>>
Cc: 
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
 
<openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] [kolla] Inviting Operators to participate in 
the specification of a new deployment tool


Just to chime in here,


I don't think its fair to say that we're not following "best practices" in OSAD 
though I will agree that OSAD is not following "Dockers best practices".​ We're 
using containers (LXC) for the purpose of network and service separation as 
well as enabling better usage of system resources while providing a deployment 
scale. We have the ability to deploy in container or on baremetal and have 
chosen to deploy services like Nova Compute and Swift Container services on 
physical hosts because it makes better sense to allow a service


we are following administrative best practices in terms of Linux and OpenStack 
operational expertise. The eithre ethos of LXC is to treat them containers like 
light weight virtual machines the idea that containers are synonymous with 
micro-services is a misnomer and a virtue perpetrated by the greater docker 
community.


We are deploying only on Ubuntu 14.04 at the moment however we're building 
everything from the upstream OpenStack source as a Python wheel which is a 
process that is platform agnostic. If RHEL support was something deployers are 
really wanting within the OSAD deployment tooling then we should talk about it 
at our community meeting[1] to get some details hammered out. It shouldn't be a 
major forklift as there's already interest in other distros as seen within our 
current pending specs with the desire to add Gentoo support[2].


[1] https://wiki.openstack.org/wiki/Meetings/openstack-ansible

[2] https://review.openstack.org/#/c/181955/


--

Kevin Carter

________________________________
From: Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>>
Sent: Sunday, June 7, 2015 6:01 PM
To: Craig Tracey; James Denton
Cc: 
openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>
Subject: Re: [Openstack-operators] [kolla] Inviting Operators to participate in 
the specification of a new deployment tool



From: Craig Tracey <cr...@craigtracey.com<mailto:cr...@craigtracey.com>>
Date: Sunday, June 7, 2015 at 3:13 PM
To: James Denton <james.den...@rackspace.com<mailto:james.den...@rackspace.com>>
Cc: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>>, 
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
 
<openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] [kolla] Inviting Operators to participate in 
the specification of a new deployment tool

+1

I would much rather see this be a feature of any one of the vast number of 
deployment tools vs. creating yet another CM repo.

Craig,

Thanks for the feedback.  I deeply respect the opinion of Operators.  I do 
believe different communities of people will lead to different solutions that 
solve similar problems.  Not everyone wants a black car.

I think OSAD is great tech, but doesn’t implement best practices.  For example, 
OSAD treats containers as virtual machines and doesn’t install all software in 
containers but only some software.  If there was one difference between our two 
implementation approaches, it is Kolla’s focus on best practices of the 
technology we depend on e.g. [1].

Hope that helps,
-steve

[1] http://sdake.io/2015/04/13/preserving-contaner-properties-via-volume-mounts/


On Sun, Jun 7, 2015 at 5:26 PM, James Denton 
<james.den...@rackspace.com<mailto:james.den...@rackspace.com>> wrote:
Hi Steven,

Can I ask how Kolla would differ from another project on StackForge known as 
OpenStack Ansible Deployment (OSAD)? It deploys a production-ready multi-node 
OpenStack cloud using containers and Ansible, and the team recently released 
v11 based on Kilo. Hate to see duplication of efforts here.

Thanks,
James

Sent from my iPhone

On Jun 7, 2015, at 5:17 PM, Steven Dake (stdake) 
<std...@cisco.com<mailto:std...@cisco.com>> wrote:

Hey folks,

I am the PTL for a project called Kolla.  We are currently a stackforge project 
but our developer community has tripled in size in the last few months.  Our 
community mission was originally to “containerize OpenStack” but the next 
logical step after OpenStack is containerized is deployment.  Our community 
wants to take a look at that mountain with a focus on simplicity.

I’d like to invite Operators to provide their feedback on the fledgling 
blueprint I have created to mark the Kolla community’s commitment to develop an 
Ansible deployment tool that deploys OpenStack in containers.

Please have a review and provide feedback here:
https://review.openstack.org/#/c/189157/

Regards
-steve
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org<mailto:OpenStack-operators@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to