Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: INT-1601
Change-Id: I358332725272c44535257648c7fbccaf94d2ac30
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
This patch is required for allowing machine-to-machine traffic within
ONAP cluster with no Vagrant operator involvement.
Issue-ID: INT-1601
Change-Id: I0159b3176ecb3e5783f4f87b9b507824fc411b2b
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
This patch creates operator keypair and deploys its public key to all
machines in the cluster. Previously cluster could be accessed from
OpenStack admin machine only.
Additional information added to the "all.yml*" group variables allowed
keeping current roles generic and flexible.
Issue-ID: INT-1601
Change-Id: I6b289ff9a8c9ebe04562671b8f4b4468b543723f
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Private key can be retrieved from OpenStack during keypair creation
only. Subsequent attempts to do so will result in getting an empty
string. If private key already exists on the local machine and there is
no guard local private key will be overwritten with an empty file.
This patch adds local private key guard which allows subsequent runs of
"create.yml" playbook without erasing local private key.
Issue-ID: INT-1601
Change-Id: If3b3bb088bc8a2f9494e21e1826ac68adcc7a2cb
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
As of Ansible 2.5+, the recommended way to perform loops is to use the
new "loop" keyword instead of "with_*" style loops [1].
This issue was reported by:
Bartek Grzybowski <b.grzybowski@partner.samsung.com>
[1] https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html
Issue-ID: INT-1601
Change-Id: Icf9079fc5c22ac034631397ea46d2b03fb4298ab
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
This allows easier storage quota changes (without the need to modify
flavors).
Issue-ID: INT-1601
Change-Id: I0fe7557ff6f23eb0e29314ee0d4819893583a294
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Added configuration resembles set of instances already in use for
Service Mesh Proof-of-Concept purposes. Floating IPs were disabled on
Worker and NFS nodes to limit resource usage.
Issue-ID: INT-1601
Change-Id: Ie575c37344da21e71a8e0803e2e5bd2db18d9290
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Additional OpenStack security group and its rules are required to allow
traffic to virtual machines created on DevStack. Virtual machines will
be accessible from 172.24.4.0/24 network (default public IP pool).
Issue-ID: INT-1601
Change-Id: I902f64f542197e329e21790f98662d2e408d4bb6
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
Key pair is generated upon host creation and removed after the host is
destroyed.
This patch is based on previous work by:
Krzysztof Opasiak <k.opasiak@samsung.com>
Issue-ID: INT-1601
Change-Id: I9acd0b68a3ee79a0d710c40e0a1cc8470dfacce5
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
This patch also adds Vagrant provisioners for creating and destroying
OpenStack infrastructure. These are set to never run (unless explicitly
called by the operator) because DevStack instance on a separate machine
might not be ready to provide OpenStack API.
This patch is based on previous work by:
Krzysztof Opasiak <k.opasiak@samsung.com>
Test harness is based on blog post [1] by:
Chris Morgan <me@chrismorgan.info>
[1] https://chrismorgan.info/blog/make-and-git-diff-test-harness
Issue-ID: INT-1601
Change-Id: I031ca7a5a43cca0258dc0dc9e0339182c431898a
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|