It can be used in a manual deployment, (i have done it) and can be somewhat of a headache :)
You may have to make some modifications to the deployer file. (.yaml) Make sure that all of your bare metal hosts, if not the same type, share the same physical nic assignments. Meaning all of the hosts have the same corresponding Eth0 and Eth1 and that they are wired appropriately. That is the real key to making openstack-base work. This will allow neutron to do it's job and route traffic accordingly. Note: there are a few more "gotchas" to deploying in a manual environment (you may or may not run into) , in context to your original question here is the networking answer. If you have a host in the cluster that does not use "Eth0/Eth1" then you will run into problems down the road. If all of your hosts use something other than Eth0/Eth1, make sure you update the yaml file "ext-port" to reflect that. for Neutron - Gateway. http://bazaar.launchpad.net/~charmers/charms/bundles/openstack-base/bundle/view/head:/bundle.yaml Lines 191-201 neutron-gateway: annotations: gui-x: '0' gui-y: '0' charm: cs:trusty/neutron-gateway-9 num_units: 1 options: ext-port: eth1 openstack-origin: cloud:trusty-liberty to: - '0' On Wed, Mar 9, 2016 at 9:40 PM, Frank Ritchie <[email protected]> wrote: > Hi all, > > I have a question about the openstack-base charm bundle. > > Can the bundle be deployed to an existing manual juju environment? > > If so, how should the 2 nics be configured prior to deployment? > > thx > Frank > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
