summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-06-08Do not create files when check connectivityMichal Skalski1-1/+1
Change-Id: If0ab25ee843f9892510da3d3c8d1f10a54440545 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-06-06Merge "Build odl plugin for mitaka"Michal Skalski7-95/+298
2016-06-02Build odl plugin for mitakaMichal Skalski7-95/+298
Change-Id: I59b96a424a753f880b4ac16abd806851ad3f9533 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-06-02Download deployment config after modificationPeter Barabas1-0/+6
Modified network or interface configurations were not reflected in the deployment config, resulting in faulty node configurations. Change-Id: I4ca20702c0171e7995f2b4f46317557ec9d5beac Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-06-02Merge "Auto deploy corrections for Fuel 9.0"Stefan K. Berg3-2/+3
2016-06-01Merge "docs: Mitaka Build req: Add p7zip-full."Jonas Bjurel1-0/+2
2016-06-01docs: Mitaka Build req: Add p7zip-full.Alexandru Avadanii1-0/+2
Build system uplift to Fuel 9.0/Mitaka now requires `7z` cmd utility also on the builder host (not only inside docker containers), so document this as a prereq in the build instructions. [1] https://gerrit.opnfv.org/gerrit/#/c/13919/ Change-Id: Icb57ac58c499272fce0a27bb2d25383e933c7814 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-06-01Auto deploy corrections for Fuel 9.0Stefan K. Berg3-2/+3
- The auto deployer's detection of nodes being up corrected as "fuel node" now returns "1" instead of "True" to denote that the node is up. - The location of bootstrap_admin_node.sh has changed so the detection of whether the Fuel node installation needed a correction for the deployer not to throw an exit code and terminate prematurely. - Small fix: deploy.py is now executable (just a chmod change). Change-Id: I8fed7bafe6912f8b4278619bbdaa16577a82737b Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-06-01Clean up after ourselvesPeter Barabas1-0/+2
Change-Id: Id7579ef618b8cd922de325d9dc1c0b7a6c5587a7 Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-05-31A small edit for the uplift to Mitaka from LibertyDaiel Smith1-1/+1
Signed-off-by: Daiel Smith <daniel.smith@ericsson.com> JIRA:0
2016-05-31common.py: catch stderr in exec_cmdJosep Puigdemont1-6/+6
When running commands with exec_cmd(), the stderr of the command is sent to /dev/null and ignored, and only stdout is retrieved. Thus, when a command fails and check is enabled, only the output of stdout is presented to the user, which normally holds no information about the error. In this patch we retrieve stderr, and when an error occurs, an exception is raised with that message. Fixes https://jira.opnfv.org/browse/FUEL-142 Change-Id: I3940e1a43963a6abec362481b1d4ce7bd7cb816d Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
2016-05-31Merge "Build system uplift to Fuel 9.0/Mitaka"Stefan K. Berg22-2438/+189
2016-05-30Merge "Remove residual Lab & configuration DEA and DHA from the unprotected ↵Jonas Bjurel28-9381/+0
Fuel repo"
2016-05-30Build system uplift to Fuel 9.0/MitakaStefan K. Berg22-2438/+189
Switching to Fuel 9.0/Mitaka for the build system. Overhaul of the patching mechanism. As bootstrap_admin_node.sh has been transitioned into an RPM (fuel-support), the lazy designer found it more simple to patch that script during the Fuel build phase than at the OPNFV ISO generation. The patch mechanism has been changed to a normal context diff instead of the orig/modified file tuples previously used. Hopefully this will require fewer manual rebases (may the fuzz be with us!). Also the ks.cfg patching has transitioned to a context based ordinary patch for the same reasons, but this is as before taking place during OPNFV ISO generation. Patch naming made more descriptive. The reaping mechanism has been slightly modified due to a change in the naming of the node files when these are generated by the Fuel CLI. IMPORTANT 1: The package cache mechanism is currently disabled, it is only possible to install Fuel with a direct internet connection. This will be fixed in a later change set! IMPORTANT 2: All plugins has been disabled! As you have re-certified your plugin with Fuel 9.0, please re-enable it in build/Makefile! Change-Id: Ia918d16a74b68f89d178e06befe6e8a7a9367bf9 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-05-25Merge "More rigorous Fuel environment check"Jonas Bjurel1-2/+4
2016-05-24Merge "docs/install-instr: Add target specific cfg sect."Jonas Bjurel3-1/+50
2016-05-20More rigorous Fuel environment checkPeter Barabas1-2/+4
get_env() used to raise an unhandled exception when reap.py was run on a Fuel node which didn't yet have an environment set up. Change-Id: I07c37db2d80e416d26fa4fb4907f4e438f1c44e5 Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-05-19Remove coexistence configuration from post scriptManuel Buil1-13/+0
This is not more needed as the config comes from FUEL ODL plug-in Change-Id: Ie09a52ac3919ac641924d41431dc000910e6d4f4 Signed-off-by: Manuel Buil <manuel.buil@ericsson.com>
2016-05-13docs/install-instr: Add target specific cfg sect.Alexandru Avadanii3-1/+50
Fuel 8.0 adds support for setting up "Offloading Modes" for target nodes. Document how this features should be used (and why/when it's necessary), and also its common limitation of not being applied during Verify Networks step (see related Fuel bug report [1]). While at it, fix minor reference to branch in git tag checkout instructions, as we'd be in detached HEAD and not on a new branch. [1] https://jira.opnfv.org/browse/FUEL-134 [Alexandru.Avadanii@enea.com] Only minor edits and prepared for upstreaming, this is mostly based on previous work from Florin. Change-Id: If7a8ca44541903dbeb6db36bc64fe56b132165cb Signed-off-by: Florin Dumitrascu <florin.dumitrascu@enea.com> Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-12Merge "docs/release-notes: Add protocol handler to ref."Jonas Bjurel2-2/+2
2016-05-12Merge "Adjust kernel numbers comparison"Michal Skalski1-3/+2
2016-05-12docs/release-notes: Add protocol handler to ref.Alexandru Avadanii2-2/+2
Doc build fails to create a link for www.opnfv.org because it does not explicitly specify the protocol handler. Make doc build happy by adding "http://" prefix. Change-Id: I7dc9c362f13bac1687d139942826eb1208556a37 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-12docs/install-instr: Fix git clone URL for HTTPS.Alexandru Avadanii1-2/+2
Drop unnecessary <user>@, not needed for http downloads. Also, fix typo (missing letter) in opnfv.org domain name. While we're at it, fix small typo in Ceilometer name too. Change-Id: I2c3341689b7a7808863906700342e62e707246e9 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-12Merge "docs/build-instr: Fix git clone URL for HTTPS."Jonas Bjurel1-4/+11
2016-05-12Remove residual Lab & configuration DEA and DHA from the unprotected Fuel repoJonas Bjurel28-9381/+0
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>
2016-05-11Merge "deployment.py: stdout not consumed when deploying changes"Jonas Bjurel1-3/+9
2016-05-11docs/build-instr: Fix git clone URL for HTTPS.Alexandru Avadanii1-4/+11
Fix wrong https git clone URL, 29418 port should be used only for SSH. While we're at it, add some bash code-block markup to bash commands. Change-Id: Ie95a4c170b70bcc3da5d4d59260d61fbd5f2a9f3 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-11Adjust kernel numbers comparisonMichal Skalski1-3/+2
With current solution kernel 4.2.0 is treated as earlier version, final comparison is: 42 < 319. This change will compare coresponding numbers of installed kernel with required version. Change-Id: Iac3aed0eb21ac8ad3138c2169299ca3b43e6e663 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-05-11Merge "The configuration of the coexistence between SFC and Netvirt is added"Nikolas Hermanns1-0/+13
2016-05-10Merge "deploy.sh: do not expect a parameter for -h"Jonas Bjurel1-1/+3
2016-05-10The configuration of the coexistence between SFC and Netvirt is addedManuel Buil1-0/+13
Change-Id: I3ce03c38677ac67df3aae0363048be21b7939bde Signed-off-by: Manuel Buil <manuel.buil@ericsson.com>
2016-05-10Merge "Reflect new deploy.py options in README"Daniel Smith1-17/+26
2016-05-10Merge "Use US keyboard layout on the console"Daniel Smith14-15/+15
2016-05-09Merge "Fix handling of relative ISO path on the CLI"Stefan Berg1-3/+4
2016-05-09Use US keyboard layout on the consolePeter Barabas14-15/+15
Change-Id: I40942c7181daf5efd1640a03471e91df82548073 Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-05-06Reflect new deploy.py options in READMEPeter Barabas1-17/+26
Change-Id: Id22ae685f324b58d07bd0c5256f3dbf55672776e Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-05-03deployment.py: stdout not consumed when deploying changesJosep Puigdemont1-3/+9
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>
2016-04-30deploy.sh: do not expect a parameter for -hJosep Puigdemont1-1/+3
If -h was given as a parameter to the script, it would report an error as it expected a parameter, and if it was called as the only parameter, it would run deploy.py as if "old style" parameters had been given, thus showing the usage for the python script, instead of the expected usage message for this script. Update the usage message to include -h. Change-Id: I0930936962c1cb479ec4409ff114cd60a386b276 Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
2016-04-29Merge "Updating project lead, and link of approval"Jonas Bjurel1-3/+3
2016-04-29Merge "Add a dha adapter python file for ZTE hardware."Jonas Bjurel3-1/+53
2016-04-29Updating project lead, and link of approvalAric Gardner1-3/+3
Change-Id: Id265bb022a4c509e642e8f8b61a65c5cfb05c1b7 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-04-28Merge "Clean up scenario files"Jonas Bjurel54-3949/+19
2016-04-28INFO file updated with Greg and Nikolas as committersJonas Bjurel1-0/+2
Change-Id: I9a64e5948e159362cb851777db6de41eccb2a599 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-04-28Fix handling of relative ISO path on the CLIPeter Barabas1-3/+4
Change-Id: I32878726432c3d883f0b33bdd2c836b0770e734f Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-04-28Clean up scenario filesPeter Barabas54-3949/+19
- 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>
2016-04-28Add a dha adapter python file for ZTE hardware.wu.zhihui3-1/+53
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>
2016-04-27Updated documentation for Brahmaputra 3.0 follow-up releaseJonas Bjurel5-44/+58
READY TO MERGE Change-Id: Ic481f02375af9be1642791fa6d96856a453c4f29 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-04-26Merge "configure_environment.py: quote environment name"Michal Skalski1-1/+1
2016-04-26Merge "Using VLAN segmentation for the NFV-OVS scenarios. Unfortunately this ↵Jonas Bjurel3-2/+524
scenario is hardwired to work with Ericsson POD-2 only"
2016-04-26Using VLAN segmentation for the NFV-OVS scenarios.Jonas Bjurel3-2/+524
Unfortunately this scenario is hardwired to work with Ericsson POD-2 only Change-Id: I3a0b56d7ff71e0ec9cd97b8ef5946fb438d43e62 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>