# Deploy RancherOS with rancher api and openstack

**URL:** <https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436>\
**Category:** RancherOS\
**Created:** [July 18, 2016, 1:20pm UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436 "2016-07-18T13:20:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rhoa](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@Rhoa](https://forums.suse.com/u/Rhoa)\
**Post date:** [July 18, 2016, 1:20pm UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436/1 "2016-07-18T13:20:41Z")

</div>

Hi,

Is it possible to specify a “Configuration Drive” to deploy a OpenStack host with API and rancher Machine Driver ?

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [September 9, 2016, 9:08pm UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436/2 "2016-09-09T21:08:08Z")

</div>

We are just calling docker-machine drivers for Openstack and it looks like they don’t have that option in their driver.

> **[OpenStack](https://docs.docker.com/machine/drivers/openstack/)**
>
> Create machines on OpenStack Mandatory: --openstack-auth-url: Keystone service base URL. --openstack-flavor-id or --openstack-flavor-name: Identify the flavor that will be used for the machine. --openstack-image-id or --openstack-image-name: Identify...

---

<div class="post-metadata">

**Author:** ![aaron-trout](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/aaron-trout/32/1941_2.png) [@aaron-trout](https://forums.suse.com/u/aaron-trout)\
**Post date:** [December 14, 2016, 9:27am UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436/3 "2016-12-14T09:27:10Z")

</div>

This is unfortunate because it means using RancherOS in Rancher is not possible if you happen to be using Openstack.

We have an on-premise Openstack deployment (private cloud) and I’ve deployed a Rancher master server on RancherOS, but the worker nodes I’ve had to put on Ubuntu.

An easier fix / path of less resistance might be to support reading the config in from the Openstack metadata service in RancherOS instead of requiring the config drive.

---

<div class="post-metadata">

**Author:** ![joshwget](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/joshwget/32/704_2.png) [@joshwget](https://forums.suse.com/u/joshwget)\
**Post date:** [January 3, 2017, 3:31am UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436/4 "2017-01-03T03:31:03Z")

</div>

You can file an issue in [rancher/os](https://github.com/rancher/os/issues) to support this. I’m not sure if this solution would still require any additional options in Docker Machine though.

---

<div class="post-metadata">

**Author:** ![duck1123](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/duck1123/32/1330_2.png) [@duck1123](https://forums.suse.com/u/duck1123)\
**Post date:** [January 11, 2017, 6:02pm UTC](https://forums.suse.com/t/deploy-rancheros-with-rancher-api-and-openstack/3436/5 "2017-01-11T18:02:45Z")

</div>

Looks like there’s an open issue for this, but it has been open for some time.

[https://github.com/docker/machine/issues/3246](https://github.com/docker/machine/issues/3246)