| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
JIRA: AUTO-38
- Issues in OpenStack SDK 0.13 were fixed in new release 0.14
- revisited the script, made some changes (delete interfaces before
deleting router)
- Script now fully works: creates all objects, and can be used also
for deleting (in a clean-up job for example)
- resilient to re-runs: can attempt to re-create, won't crash if
objects already exist (existence tests work, thanks to SDK 0.14
fix). Likewise, can attempt to re-delete (no crash).
- next steps will be:
* update created objects based on ONAP-B requirements
(current: still from Amsterdam; should be quite similar)
* script to ensure Python3 and SDK are installed, and to
ensure files are there (clouds.yaml, .img)
* chain in CI pipeline: Fuel/MCP install, and this script
Patch 2:
made changes to address the comments
- fixed the summary (works in any execution case), tested on hpe12
- researched the URL support (use image proxy), but did not try yet
(need to merge this for 6.2)
Change-Id: Ibf647e33428c98a6fec17eda0a41e9ee11cc8085
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
(cherry picked from commit c8f22d584e6bb23634d12e40d66400a718d5cbc7)
|
|
JIRA: AUTO-38
Automated configuration of an OpenStack instance for ONAP
Updates:
- using identity proxy now works
- attaching a gateway to a router now works (at router creation)
- added --debug and --delete options
- added summary display at the end, with network IDs (for YAML files)
Not yet working:
- existence tests and deletions, waiting on OS-SDK bug fix
(equality test in Resource.py)
- assigning user to project using SDK identity proxy
(no such method yet in SDK identity proxy)
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
Change-Id: I69c922c1e3a3ab94988d470637251598124b98ac
(cherry picked from commit b718a43380376d2b19222c4203c97a95ca849ae8)
|
|
Initial code (based on OpenStack SDK Python client) for configuring
an OpenStack instance (e.g. installed by Fuel/MCP) and prepare it for
ONAP (especially, to host VM-based VNFs).
Currently works: creation of networks, routers, router interfaces,
security groups (accessing VMs also works with compute proxy, but is
not used for this program).
Current issues: identity proxy (so can't create projects and users),
adding gateway to router, deletions
This script could be launched automatically right after installing
OpenStack, and before installing ONAP (so as to grab OpenStack info
to be fed into ONAP configuration files). Also, VNF YAML/ENV files
can be populated once the OpenStack instance is ready for ONAP.
Note: plenty of test and debug lines, which would be removed.
This changeset is just to capture a snapshot of this effort in the
Auto repository, and to enable reviews and feedback.
Change-Id: If3b69b5a9a45905455db3a4eae0c6b336ce7447b
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
(cherry picked from commit 5ba5768eee759f9d09d20a2fe6af6b4fe9463d54)
|
|
JIRA: -
Misplace public key and private key
Change-Id: Iae694cfdab00500af863c934f5924693d5bab5d1
Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
(cherry picked from commit a85a3366e4ca2094facf69b696e0c03e97ab45dc)
|
|
JIRA: Auto-5
Setup ONAP environment on OpenStack. Develop Using
Python considering its proved performence within
OPNFV testing project, and with its rich library we
can operate REST calls and json parsing in a more
elegant way, also others can reuse the existing
module to develop use cases and test cases.
Main workflow:
1. prepare OpenStack to launch ONAP (images, security
rules, keypair, etc)
2. launch ONAP stack
Change-Id: Id99affccbcaa86be134a535f89b26c54ad137e21
Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
|
Gerard Damm
Harry Huang