Open Stack

Thiago, Sorry for not replying inline, OWA is all I have access to today.


We too have the ability to run everything on an AIO (all in one) which can be accomplished with a single command: 

---
# Command to run an AIO
bash <(curl -s https://raw.githubusercontent.com/stackforge/os-ansible-deployment/master/scripts/run-aio-build.sh)
---

Documentation on building a development stack [0] - Official documentation that we've been maintaining [1]


This AIO process is what we do to test gating on every commit made to the upstream project and it creates several dummy interfaces to make it mimic a real world deployment, even if its on a single host, and has the ability to test clustered Galera, Rabbit, Repos, etc...


If you don't want to use our containerized architecture you don't have to. Simply set the flag `is_metal: true` within the conf.d items that you don't want to run within a container. Information on how this can be done can be read / seen here: [2]  -- essentially, set that flag and all container creates / management will be ignored. This option can be set to various group types and can be mixed/matched as you see fit.


We are not using Ubuntu packages or any OpenStack packages from any distro; in truth, we have no intention to do so, unless there's someone within the community that wants to contribute and maintain that type of deployment. We've found that we're able to ensure better consistency and stability when using source. Additionally, we can test/implement upstream bug/security fixes faster without having to wait on package fixes from the distros or having to deal with some of the brokenness they've provided.


As for backporting fixes or custom code you OSAD can help you do that already by simply maintaining your own git sources. The OSAD project is able to build from and use just about anything. This is enabled and covered here: [3] I'd be happy to cover more of that if it would be of interest to you. IMHO building form git in this manner will help with many of the packaging problems that can arise from using the PPA system.


We do not support OvS yet. However, we'd love someone to come along and want to contribute some bits to make it supportable. The framework itself is robust enough to support a variety of network providers but as I've mentioned before, we simply need contributors whom want to see these types of features within the project, PRs are always welcome.


Thiago, stop by the #openstack-ansible IRC channel there's almost always someone in channel and we'd be happy to help answer any of the questions that you or your team may have and if there's sufficient interest I'm sure we can align on some of your goals to progress our collective projects.

--

Kevin Carter
IRC: cloudnull

[0] - https://github.com/stackforge/os-ansible-deployment/blob/master/development-stack.rst
[1] - http://osad.readthedocs.org/en/latest/
[2] - https://github.com/stackforge/os-ansible-deployment/blob/master/etc/openstack_deploy/env.d/cinder.yml#L53-L57
[3] - https://github.com/stackforge/os-ansible-deployment/tree/master/playbooks/defaults/repo_packages

________________________________________
From: Martinx - ジェームズ <thiagocmartinsc at gmail.com>
Sent: Monday, August 31, 2015 11:12 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [ANN] OpenStack Kilo on Ubuntu fully automated with Ansible! Ready for NFV L2 Bridges via Heat!

Hey guys,

 I know, the Ansible deployment
(https://github.com/stackforge/os-ansible-deployment) is impressive...

 But, for our need, we required something much simpler, that could be
deployed in an all-in-one fashion, without LXC containers for each
service, Ansible against localhost to simplify even more and using
only one NIC to begin with (br-ex and vxlan data net are being used
against a dummy0 and dummy1 interfaces).

 So, the Stackforge deployments is far too much complex for what we need.

 We found some limitations and a serious bug on Linux (I'll report
later), when using it with Linux Bridges (OVS is a requirement here,
specially because we want to try DPDK later).


 Concerns about "stackforge/os-ansible-deployment":


 1- It does not make use of Ubuntu OpenStack packages, it installs
everything from Git and Python PIP (we don't like it this way, why not
use Ubuntu packages? No reason...);

 2- It uses Linux Bridges, but unfortunately, it is not ready yet for
NFV deployments (where an Instance acts as a L2 Bridge), it simple
doesn't work / can not be used for "L2-NFV" (we found a very serious
BUG on Linux);

 3- Very hard deployment procedure and it needs more that 1 physical
box (or more than one VM, 1 for Ansible host, 1 for controller and its
containers, 1 for Net node, and the compute nodes).


So, we need Open vSwitch (not supported by "os-ansible-deployment",
right?), OpenStack Ubuntu packages from Cloud Archive and a very
simple setup / topology (no containers / all-in-one physical box).

Basically, that's why I created this new Ansible playbook.

You can install OpenStack on Ubuntu LTS with 1 command:

---
bash <(curl -s https://raw.githubusercontent.com/sandvine/os-ansible-deployment-lite/kilo/misc/os-install.sh)
---

Also, we need to patch Heat, to add support for "port_security_enabled
= False" via templates, that's why we're maintaining an Ubuntu PPA. To
backport things from Liberty, to Kilo.

We want to contribute with Ubuntu packaging, report bugs and etc,
that's why we're using it (instead of installation from Git).

Thoughts?

Best,
Thiago

On 26 August 2015 at 12:01, Kevin Carter <kevin.carter at rackspace.com> wrote:
> +1 I'd love to know this too.
>
> Additionally, if vagrant is something that is important to folks in the greater community it would be great to get some of those bits upstreamed.
>
> Per the NFV options, I don't see much in the way of OSAD not being able to support that presently, its really a matter of introducing the new configuration options/package additions however I may be missing something based on a cursory look at your published repository. If you're interested, I would be happy to help you get the capabilities into OSAD so that the greater community can benefit from some of the work you've done.
>
> --
>
> Kevin Carter
> IRC: cloudnull
>
>
> ________________________________________
> From: Thierry Carrez <thierry at openstack.org>
> Sent: Wednesday, August 26, 2015 5:15 AM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [ANN] OpenStack Kilo on Ubuntu fully automated with Ansible! Ready for NFV L2 Bridges via Heat!
>
> Martinx - ジェームズ wrote:
>>  I'm proud to announce an Ansible Playbook to deploy OpenStack on Ubuntu!
>>  Check it out!
>>  * https://github.com/sandvine/os-ansible-deployment-lite
>
> How does it compare with the playbooks developed as an OpenStack project
> by the OpenStackAnsible team[1] ?
>
> Any benefit, difference ? Anything you could contribute back there ? Any
> value in merging the two efforts ?
>
> [1] http://governance.openstack.org/reference/projects/openstackansible.html
>
> --
> Thierry Carrez (ttx)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev