[Openstack-operators] [kolla] Inviting Operators to participate in the specification of a new deployment tool
Kevin Carter
kevin.carter at RACKSPACE.COM
Mon Jun 8 14:28:51 UTC 2015
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) <stdake at cisco.com>
Sent: Sunday, June 7, 2015 6:01 PM
To: Craig Tracey; James Denton
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] [kolla] Inviting Operators to participate in the specification of a new deployment tool
From: Craig Tracey <craig at craigtracey.com<mailto:craig at craigtracey.com>>
Date: Sunday, June 7, 2015 at 3:13 PM
To: James Denton <james.denton at rackspace.com<mailto:james.denton at rackspace.com>>
Cc: Steven Dake <stdake at cisco.com<mailto:stdake at cisco.com>>, "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at 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.denton at rackspace.com<mailto:james.denton at 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) <stdake at cisco.com<mailto:stdake at 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 at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150608/84cf951a/attachment.html>
More information about the OpenStack-operators
mailing list