With the current local.conf it is not possible to use floating-ips
to access an instance.
This patch extends and refactors the local.conf, that devstack creates
2 networks. A public network (used for floating ip) - public, and a
private network where the instances get attached to - provider.
In addition the ovs is configured to be able to deal with both networks.
However one manual step is required. The bridge br-provider needs to be
created manually before stack.sh is run.
Change-Id: I776552c41161d53d33ad9c6c750f47ef6d5ccce6
This is in connection with the minimum value assigned to the max-memory
parameter in local.conf under dpm section.The default value of
reserve_host_memory is 512Mb by which it blocks 512Mb of memory on the
host this means to launch an instance on a host 1024 is the minimum
memory that is needed as 512Mb is being reserved inorder to mitigate
this issue the reserved memory is made 0.
Change-Id: I05ee4275cd5d80b1edb614d94fe0b038551bc3cc
There is a NumInstancesFilter which can be used to filter the number of
instances that are supposed to be launched on the host this replaces the
work that is planned for max_instances config parameter to perform.
It is removed as the main functionality of this parameter is not yet
implemented in the code.
Change-Id: Ie545a5f74f7b63ea56812577c201fcb443014998
This patch extends the local.conf that the singlenode is able
to host an openstack dhcp server and openstack router.
Change-Id: I9e8623c006ac89552c42316ee889c16f4a7b5aa1
Patch [1] removed the VLAN support from networking-dpm. Now attaching
an instance to a VLAN network results in an error message. Therfore
we need to adapt the devstack local.confs (which created a VLAN
network by default).
[1] https://review.openstack.org/#/c/429546/
Change-Id: I2143ea4ad3d40aa922eae0d57ec3935259278b24
It is not applicable any more, as always a FC cinder backend
is required to launch an instance. This is covered by the local.conf
"local.conf.singlenode.nova_neutron_storage"
Change-Id: I434844e2423b6097b89e3f3521204f753dcbf420
networking-dpms 'physical_adapter_mappings' parameter got renamed
to 'physical_network_adapter_mappings'. This patch reflects this
change in nova-dpms devstack local.confs.
Change-Id: I6d33ad8047149bf5bc05e254ab63570d5f97fa68
Closes-Bug: 1661563
Manual updation of params could be error prone
for same set of attributes, hence adding new
params which has to be configured once by the
administrator which will be referred to in the
rest of the local.conf file
Change-Id: I17e19fbb4328dbb8ca7b02f1afd35baa9f942718
Moved the default.host section of the local.conf from the
neutron.conf file into the neutron plugin conf file. Technically
both works with devstack, but to make more clear where the option
belongs to it got moved there.
Change-Id: I636bf37b290f3abf7da884017e25d1aebd2bc2d9
Networking-dpm changed a config option from using cpc_name to
cpc_object_id. This patch reflects this in the devstack local.conf.
Change-Id: Id574493104ae4cd9c9a954f93297434be401d3ac
The DPM driver manages so-called "cpc-subsets". Basically, this is
a logically portion cut out of a system z CPC. For the Nova driver,
this emulates a "host". This results in this multiplicity:
DPM Driver 1 --- 1 CPC-subset (=host) * --- 1 CPC
Having the two config options "[DEFAULT].host" and "[dpm].host", which
mean the same thing, could be confusing for a user. Also, this can
lead to issues if both are not in sync, for example during the
Nova<->Neutron communication where the NICs get created.
To resolve this, this change removes the config option "[dpm].host"
and uses "[DEFAULT].host" only. As the config option wasn't yet part
of any release, we don't need to do the usual deprecation policy.
closes bug: 1655043
Change-Id: Ibb2c23e248c4390e2ec19e7aa9811abdc24fea25
Reason for the change is that the HMC API book does not mention
anywhere that the format of the ID is a UUID, and the name of the
resource property is "object-id". This change set changes the
name of the DPM config option "cpc_uuid" to "cpc_object_id",
and the devstack variables CPC_UUID to CPC_OBJECT_ID, and
updates any use of that and the unit testcases accordingly.
Change-Id: I6153ac791d4296101dc00f23dfb7fb7c3d2fee2c
Partial-Bug: 1659304
Signed-off-by: Andreas Maier <maiera@de.ibm.com>
+ Updated tox.ini to install nova
+ Modified tox_install script to install zhmcclient requirements and removed
conditional nova installation check because new folder nova introduced for
devstack setup always returns true for the check that verifies if nova is
already installed
blueprint: devstack-setup-nova
Change-Id: I0c16e4bdda38eb331fa76010e39b5d8457475af4
Vu Cong Tuan