This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
salt4nfv [2015/01/22 14:20] Iben Rodriguez fixed url link |
salt4nfv [2015/02/19 23:30] (current) Iben Rodriguez |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== SaltStack 4 NFV ====== | ||
- | Spirent has built and released a setup of salt scripts to build an openstack platform. These scripts are being enhanced and extended to support the OPNFV. Anyone wishing to collaborate on this parallel effort is welcome to join. | + | Spirent has partnered with Cloudbase Solutions to build and release a suite of SaltStack scripts for deploying OpenStack, supporting Icehouse and Juno releases on multiple target hardware platforms. These scripts are being enhanced and extended to support the OPNFV scenarios. Anyone wishing to collaborate on this parallel effort is welcome to join. |
It is recognized that there are many choices available for: | It is recognized that there are many choices available for: | ||
Line 10: | Line 10: | ||
* networking solution (vswitch, contrail, etc) | * networking solution (vswitch, contrail, etc) | ||
- | Regarding devops tools: there are certainly many tools available each with their own pros and cons. Each organization will use the one best suited to their needs many times based on personal experience of the sysadmins. Changing from one tool to an other is no easy task as the library of scripts can contain years of investment from hundreds of contributors. More and more these devops tools have moved beyond just the ability to update operating system configuration files. Now there are solutions to deploy fully working, highly secure and available, multi-node openstack platforms. Some organizations might use fuel, some native puppet, or packstack (RDO), others salt, ansible, chef, while some hard core sysadmins might use bash. | + | Regarding devops tools: there are certainly many tools available each with their own pros and cons. Each organization will use the one best suited to their needs many times based on personal experience of the sysadmins. Changing from one tool to another is no easy task as the library of scripts can contain years of investment from hundreds of contributors. More and more these devops tools have moved beyond just the ability to update operating system configuration files. Now there are solutions to deploy fully working, highly secure and available, multi-node openstack platforms. Some organizations might use fuel, some native puppet, or packstack (RDO), others SaltStack, ansible, chef, while some hard core sysadmins might use bash. |
- | With this in mind we started a project last year to build a flexible deployment framework to allow a profile to be built for each of the desired attributes. Based on the desired profile a machine can be configured with salt stack in a repeatable manner. This allows us to tear down and rebuild machines multiple times a day as part of our automated testing solution. | + | With this in mind we started a project last year to build a flexible deployment framework to allow a profile to be built for each of the desired attributes. Based on the desired profile a machine can be configured with SaltStack in a repeatable manner. This allows us to tear down and rebuild machines multiple times a day as part of our automated testing solution. |
We are working closely with the OpenDaylight and OpenStack developers to bring more components into this testing framework. | We are working closely with the OpenDaylight and OpenStack developers to bring more components into this testing framework. | ||
- | Since the OPNFV Getting Started project is not using Salt it is our intention to follow along as closely as possible to provide a platform with similar capabilities. The end result should be the same: | + | Since the OPNFV Getting Started project is not using Salt, it is our intention to follow along as closely as possible to provide a platform with similar capabilities. The end result should be the same: |
* Centos 6.5 or 7 or Ubuntu 12 or 14 OS (we support all 4) | * Centos 6.5 or 7 or Ubuntu 12 or 14 OS (we support all 4) | ||
Line 25: | Line 25: | ||
* all machines are requested and provisioned via the NephOS API which allows pxeboot and manages the networks | * all machines are requested and provisioned via the NephOS API which allows pxeboot and manages the networks | ||
- | These salt scripts are available in [[https://github.com/cloudbase/salt-openstack|git]] and are being developed and pushed upstream to the main salt project by our partners [[http://www.cloudbase.it/|Cloudbase Solutions]] | + | These salt scripts are available in [[https://github.com/cloudbase/salt-openstack|git]] and are being developed and pushed upstream to the main SaltStack project by our partners [[http://www.cloudbase.it/|Cloudbase Solutions]] |
+ | |||
+ | ====== Todo Wish List ====== | ||
+ | |||
+ | * Look at integrating these SaltStack scripts with Foreman for bare metal provisioning: [[https://github.com/theforeman/foreman_salt/wiki|https://github.com/theforeman/foreman_salt/wiki]] |