Openstack Kolla Ansible reconfigure all compute node to enable provider network - openstack

May I ask how to reconfigure all compute node to enable provider network in Kolla Ansible openstack?

As I know, openstack will support to create provider network while kolla-ansible deploy success.
Because it enable the relevant composes default in all-in-one or multinode file, something like this:
# Neutron
[neutron-server:children]
control
[neutron-dhcp-agent:children]
neutron
[neutron-l3-agent:children]
neutron
While neutron-l3-agent enable default, you could also create Self-service network not only Provider networks.
IIUC, you could create the provider network and launch instance with this network, like the documentation describe:
$ openstack network create --share --external \
--provider-physical-network provider \
--provider-network-type flat provider
One more thing, your network infrastructure (such as switch or router) should configure correctly at first while you using it.

Related

How to attach static IP to a virtual machine using gcloud?

Trying to attach existing reserved IP address to a new virtual machine using gcloud
it's easy to do in the console, can't find a way how to do it using gcloud
See:
link
gcloud compute instances create [INSTANCE_NAME] --address [IP_ADDRESS]

Use more than one physical interface on devstack ocata

I have a barebones PC with 6 physical interfaces to 'play' around with devstack. I'd like to deploy VMs on it and connect them to different Ethernet interfaces. Currently, I'm only able to use the interface associated to the br-ex bridge. I've tried to define several OVS bridges and assign the physical interfaces to different bridges. I try to define a mapping with more than one bridge, but that doesn't seem to work.
Has anyone had any success on this.
Thanks, /PA
You will need to create "provider networks", which allow you to associate neutron networks with specific physical interfaces. You can find documentation on creating provider networks in the install guide.
Once everything is configured correctly, you can attach new Nova servers to your provider networks by passing the appropriate --network argument when you boot a new server.

Cloudify 3.3 - Use of existing network (no Floating IP)

we want to configure a Cloudify Manager into an OpenStack project in which there is only an external network (named public_net), with public IP addresses.
In other words, each Cloudify VM (both Manager and Application) should be attached to the external net (no Floating IP).
The Cloudify CLI, on the other hand, was created out of OpenStack.
How should we configure the OpenStack plugin to implement this scenario?
The Cloudify manager if bootstrapped with the Openstack blueprint will be configured to two networks:
The network that it can connect to the OpenStack API (external network)
A management network that it will create.
If you want to use the external network for the management network, you should change the blueprint so it will have this network as an external resource (external_resource: true) and set the name of the network to public_net.
your blueprint will look like this:
management_network:
type: cloudify.openstack.nodes.Network
properties:
use_external_resource: true
resource_id: public_net
openstack_config: *openstack_configuration

How to integrate Opendaylight with OpenStack? How does Opendaylight operate when integrated with OpenStack?

I was trying to integrate ODL with Neutron by enable odl service in the local.conf file, but it wasn't able to exit the ./stack.sh script properly.
How can I integrate both?
And how does Neutron work with and without ODL.
Neutron provides "networking as a service" between interface devices managed by other Openstack services, but it's just an API which parse messages to REAL messages in the core of the network and Opendaylight really deals with the core of the network itself.
While OpenDaylight Controller provides several ways to integrate with OpenStack, you might use VTN features available on OpenDaylight controller. In the integration, VTN Manager work as network service provider for OpenStack. VTN Manager features, enable OpenStack to work in pure OpenFlow environment in which all switches in data plane are OpenFlow switch.
So you can follow this tutorial: https://wiki.opendaylight.org/view/Release/Helium/VTN/User_Guide/OpenStack_Support#How_to_set_up_OpenStack_for_the_integration_with_VTN_Manager

Neutron Flat networking with no dhcp

I would like to configure my openstack to use IP's from the same network as my physical server. I do not want to use dhcp or floating IP's.
neutron net-create --tenant-id TENANT-ID --shared sharednet1 --provider:network_type flat --provider:physical_network physnet1
neutron subnet-create sharednet1 10.68.10.0/24 --gateway-ip 10.68.10.11 --diable-dhcp
When create an instance , Nova should able to 'inject a ip' to instance.
Is that possiable ?
How to configure it?
Please follow the basic installation guidehttp://docs.openstack.org/ for grizzly or havana in the networksection.
You can use the static IPs of your physical servers by hard coding the static values in /etc/network/interface files so that when you create your router, it will use that IP

Resources