Age | Commit message (Collapse) | Author | Files | Lines |
|
In order to make gluon really deployable some more things
need to be done:
- Add pull request 103 which add yaml files which
point to gluon puppet
- Rename the scenario to odl-gluon similar to bgpvpn
scenario
- Add tht of gluon to overcloud-deploy-functions.sh
JIRA: APEX-379
opnfv-tht-pr: 103
opnfv-puppet-tripleo-pr: 13
Change-Id: I3ccfb5a279f1df21c4da79fc47039b3c0b6e5495
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
This patch adds yardstick option to deploy settings, installs docker and
yardstick image to undercloud.
Change-Id: I3a2a1d6bcdfe5becd11d6d9f22218837c572d5da
Signed-off-by: Manjunath Ranganathaiah <manjunath.ranganathaiah@intel.com>
|
|
Now in inventory file a user can declare 'disk_device' which will allow
the user to specify which disk on their overcloud server to use for
installation. The variable can be a comma delimited list, which will
search in order post-introspection for the first device on the node that
exists. The default disk used will be sda for deployments.
Currently defining a per node disk is not supported by OSCLI, so
although defined that way in Apex inventory, only the last definition
will be used for all nodes.
Other changes include:
- Various fixes in inventory parsing
- Makes bash writing a common function
- Introspection now enabled for baremetal deployments
JIRA: APEX-296
Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-374
Change-Id: Id7509d6c6528310cefc62522d3a90ddee19146a9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Introduces new (hidden) cli option to change composable env config.
This parameter then will use the provided file, for example,
csit-environment.yaml instead of the typical opnfv-environment.yaml.
The effect is using less services required for ODL CSIT snapshots.
Note: this will not work with perf options, but those are not required
currently for ODL CSIT.
CSIT also does not need ceph, so providing a new deploy option to
allow disabling it.
JIRA: APEX-362
Change-Id: If3833b1acceeb23ef9e12c90df6cc9607bd8c724
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Also contains various network parsing fixes.
JIRA: APEX-361
Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-347
Change-Id: Ibc6d141e20faf613e0f6314286b55aff01ce862e
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Also depend on https://github.com/radez/puppet-fdio/pull/14
JIRA: APEX-337
opnfv-tht-pr: 92
Change-Id: Ic3d2f04bfd1983c38e09a2bfa3992a572fc9c6c1
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
The deploy settings values are embedded in a dictionary inside a
generic object. This patch makes the deploy settings object
a dictionary so the values can be accessed directly without
having to unnecessarily drill down through an empty object
to the dict that holds the content intended to be managed by
the deploy settings object.
- adding tests to cover DeploySettings 100%
Change-Id: I4ba625cd7b51cfb6c1f91c74f1d332d1e3dd9a8e
Signed-off-by: Dan Radez <dradez@redhat.com>
|