No unit file named firewalld in Ubuntu

[Harsh Vardhan]

In the file `kolla-ansible/contrib/dev/vagrant/bootstrap.sh` the function *prep_work* checks for firewalld. In CentOS, the daemon to manage the firewall is firewalld, but in Ubuntu it is `ufw`.

Hence the function *prep_work* will fail to disable the firewall on Ubuntu, i.e. when a development environment has been created using "ubuntu/xenial64"

[Harsh Vardhan (vharsh)]

```
ubuntu@ubuntu-xenial:~$ systemctl is-enabled ufw
enabled
ubuntu@ubuntu-xenial:~$ systemctl is-enabled firewalld
Failed to get unit file state for firewalld.service: No such file or directory
```
The second one is not equal to "enabled" as bash sees it, so the firewall will not get disabled.

[Harsh Vardhan (vharsh)]

Ref https://docs.openstack.org/kolla-ansible/latest/contributor/vagrant-dev-env.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/503693

[Harsh Vardhan (vharsh)]

I have made an extra commit by clicking the *follow-up* button. I don't know how to undo my commit in launchpad, a force push was rejected by gerrit.
Will clicking 'abandon' delete the commit or create a new commit?
Here's the link https://review.openstack.org/#/c/503934/1 this is the commit id:8cdb3b2d2c

[OpenStack Infra (hudson-openstack)]

Change abandoned by Harsh Vardhan (<email address hidden>) on branch: master
Review: https://review.openstack.org/503693
Reason: Abandoned

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/503693
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7769c65670b767e7e8b731e3f76496791a99bcee
Submitter: Jenkins
Branch: master

commit 7769c65670b767e7e8b731e3f76496791a99bcee
Author: Harsh Vardhan <email address hidden>
Date: Wed Sep 13 19:39:02 2017 +0530

    Disable firewall while setup of dev env

    Firewall managers in
    Ubuntu ufw
    Centos firewalld
    Closes-bug: #1716912

    Change-Id: I7556fcfe4947e73f4b7f4b37c2477d9694a36c26

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 6.0.0.0b2 development milestone.