Age | Commit message (Collapse) | Author | Files | Lines |
|
This needs testing!!!!
On a follow-up release, this also needs rebasement, the libvirt templates
are still in here - they shouldnt, sinse we dont want Lab specific
configs in the Fuel repo.
NOT VERIFIED
DO NOT MERGE
Change-Id: I069ced81b886405463f27f37a6ec78e3748b37b7
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
|
|
|
|
|
|
|
|
Change-Id: I40942c7181daf5efd1640a03471e91df82548073
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
Change-Id: Id22ae685f324b58d07bd0c5256f3dbf55672776e
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
During the automatic deployment, when the environment is ready to be
deployed, the deploy.py script will spawn a shell process that will
perform the command "fuel deploy-changes". The standard output of this
process is then piped to a "tee" process, which redirects the output
to the standard output of the shell process, and to a file named
cloud.log. The file is monitored by the deploy script to find out the
status of the deployment, and print it to the log file of the automatic
deployment script, including percentages for each node being
provisioned. However, the deploy script never consumes the standard
output of the shell process. If the shell process produces enough
output, its standard output buffer will fill up, thus making the tee
process block trying to write to its standard output, and the cloud.log
file will not be updated. At this point, the deploy process, which is
monitoring cloud.log, will not detect any progress in the deployment,
and eventually it will time out and assume the deployment failed,
although it might have finished fine after that.
The solution here is to remove the "tee" process from the shell command,
and instead redirect standard output to the cloud.log file.
Another solution would be to actually parse the standard output of the
shell command from the deploy script itself, but that would require a
bit more work, as reading a line at a time might block the script.
Finally, with this patch the cloud.log file won't be deleted unless the
shell process has already finished.
Change-Id: I03a77be42d220b1606e48fc4ca35e22d73a6e583
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
|
|
Change-Id: I32878726432c3d883f0b33bdd2c836b0770e734f
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
- remove release from scenario files
- remove old versions of scenario files
- remove versions from scenario file names and update scenario.yaml
- update README
Change-Id: I5203ea0794b96fb44f6a9db25b33e5066c1d9574
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
ZTE hardware need use IPMI command "chassis power cycle"
on function node_reset().
JIRA: FUEL-127
Change-Id: I286fd9cda43d2e1799b134f0a391f57d08cd1928
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
Unfortunately this scenario is hardwired to work with Ericsson POD-2 only
Change-Id: I3a0b56d7ff71e0ec9cd97b8ef5946fb438d43e62
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
The Fuel environment name may contain spaces, putting the name in quote
marks prevents the second and subsequent words from being interpreted
as other parameters by the fuel command.
The name could contain double quotes too, so this doesn't solve all
problems, but arguably the most common case.
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
|
|
|
|
Change-Id: I82ce16751b4d52d6fdb39883b730073164f9dfe0
|
|
Change-Id: I215da0a101d94e2c3fd4aeea80b98f7c9aefe0fb
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
Change-Id: I306b8260ea37fb32ef8db8cf5d4628b50328027f
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
|
|
This commit includes the bugfixes and changes
for BGPVPN_extensions and SDNVPN_feature of ODL.
Change-Id: I9832680109edae497f7a344d5626568d3a335a15
|
|
If no vm definition is give,
nothing should happen.
Change-Id: I1fd01ef43fa3e5eab4a794c63254eaf6d80fc951
|
|
|
|
|
|
Redoing this the reverted patch. The original idea
that everyone which wants to merge lists has to
code that, is not wanted. So the Exception will
become a warning.
This reverts commit 552536f5319d6ead73118d0cfd701d648e99df28.
Change-Id: Ib15541199054da27c1a2aec68b5c1436da9622c9
|
|
This commit enables the full configuration
of the VM(fuel/controller/compute)
defintion through the dha file.
Change-Id: I4e78334d1e5aec1e98667343390283587f0b3ea5
|
|
- Ceph is used with a replication factor of 1
- In no-ha, a separate node is used for ceph-osd
- In ha, one of the controllers is used for ceph-osd
Change-Id: Ibb00b385fe138374e380839fbc12067fd71c2a26
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
|
|
This reverts commit 0eabb596edefd6562a892f27f4e838d9d21c5243.
Change-Id: Ifc4cb5bd12bdf50f0dd903af66037a428aed0201
|
|
|
|
|
|
For development reason it is useable to
have an option so that everything is done
except the deploy of the openstack
environment.
Change-Id: I1f1b7f9c89ee8c9ceea96353e25a51eee53b955c
|
|
When the dic of a plugin is not fully merged
into the final dea file. When a list contains
dicts there is no merge. This commit
enables the versions list to be merged.
Change-Id: I20ff7bec74f8f71a8cd21010f44715953cd4616d
|
|
Change-Id: I6789b81186b7ede124a838a5b6668ba8326e0c0b
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
|
|
|
|
Some compones of openstack produce a lot of CPU load.
With this commit it is possible to
make more use of the Hypervisor where the virtual
nodes runs on.
Change-Id: Ide567dd0823c5526171c29073f2a36aa5f27d4b6
|
|
The plugin config 0.0.2 has some
missleading statements. At some point
in time we should delete it and
only use this one here.
Change-Id: I6ceb2d2b7379ad691e4c7116ed7bc552deffc099
|
|
Fixes https://jira.opnfv.org/browse/FUEL-100
Change-Id: Ic2e01372778720cde84d83738d8b2c85b005124a
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
A lot of diskspace is allocated although never used
this commit changes to thin provisioning
for the virtual enviroment.
Change-Id: Ia128143a3bae9f3d85a9e749319c2f5343c1df4e
|
|
|
|
Not every CPU supports apparmor and
there is no real benefit when using it
only for fuel.
Change-Id: Ibb3221b85d8565f718df9b087aa324d0f606bdee
|
|
Change-Id: I6f3f35680c9f90f99148865edf8ba905ecbb6c30
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
Change-Id: I2dc062a8b4ad7c7bc0782781565fd182d5993014
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
|
|
The SFC subproject has been developed Tacker service orchestration
for OPNFV+Apex. There was a hint that the same feature should exist
in OPNFV/Fuel too. Since We had not enough time and resource the
given implementation is proof-of-concept, a shell script based
deployment + orchestration is given. The script designed being
idempotent but lacks error handling. For Brahmaputra SR-1 a more
reliable fuel-plugin implementation will be given.
The script (poc.tacker-up.sh) is loosely integrated: the user
should transfer it to the primary controller, where the OpenDayLight
service is deoloyed and should execute the script manually. Note that
adding Tacker service to OPNFV assumes that the cluster has
fuel-plugin-ovs (with NSH support) and OpenDayLight SDN controller
(fuel-plugin-opendaylight with GBP anf SFC fearures enabled) plugins
enabled during deployment.
Change-Id: Icb582c545e163816df14fa06411aa62d0c66cd5d
Signed-off-by: ferenc Cserepkei <ferenc.cserepkei@ericsson.com>
|
|
Pleas carefully review this patch, especially the ODL features
NOT VERIFIED
DO NOT MERGE
Change-Id: Ief3fa22d5fd03c17101aef4cbe7dcf88f5f14e8c
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Change-Id: I10d3a1a9bef918005e0756d209953fa5dcc21d6c
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
|