As a devOps, I want to a documentation for using Terraform to deploy VMs on Openstack
Description
Activity
Former user June 18, 2020 at 1:06 PM
I closed the lab ticket
my bad I modified this one but I should not have, it has to be used to track your own activity here, not the project creation.
Former user June 18, 2020 at 12:58 PMEdited
Integration-Terraform created
openstack user list --project Integration-Terraform
---------------------------------------------------+
ID | Name |
---------------------------------------------------+
c0b8c33dd59940319aeb163739688445 | yoonsoon_jahng |
eed43706dd214a26a6aa544cdd5f649c | neil_derraugh |
cd1e8efd50024416ab45b8231bdb8646 | morgan_richomme |
openstack quota show Integration-Terraform
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Field | Value |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
backup-gigabytes | 1000 |
backups | 10 |
cores | 60 |
fixed-ips | -1 |
floating-ips | 10 |
gigabytes | 1000 |
gigabytes_ceph | -1 |
groups | 10 |
health_monitors | None |
injected-file-size | 10240 |
injected-files | 50 |
injected-path-size | 255 |
instances | 500 |
key-pairs | 20 |
l7_policies | None |
listeners | None |
load_balancers | None |
location | Munch({'cloud': '', 'region_name': 'RegionOne', 'zone': None, 'project': Munch({'id': '466979b815b5415ba14ada713e6e1846', 'name': 'Infrastructure', 'domain_id': 'default', 'domain_name': None})}) |
name | None |
networks | 10 |
per-volume-gigabytes | -1 |
pools | None |
ports | 500 |
project | 1068daf2aa6347a6ba9a7ef9d2a2dbd9 |
project_name | Integration-Terraform |
properties | 128 |
ram | 200000 |
rbac_policies | 10 |
routers | 10 |
secgroup-rules | 100 |
secgroups | 10 |
server-group-members | 100 |
server-groups | 100 |
snapshots | 100 |
snapshots_ceph | -1 |
subnet_pools | -1 |
subnets | 100 |
volumes | 100 |
volumes_ceph | -1 |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
you shall be able to use it now.
Please do not hesitate to report the status of your progress to Integration project. Ideally we should be able to create a CI chain showing your terraform based installation scenario.
Former user June 18, 2020 at 12:40 PM
OK what are your windriver user names, so i can give you the admin rights on the projects
Former user June 15, 2020 at 3:56 PM
Thanks @Former user
Yes, I recognize that you are planning some cleaning up. You can assign some resources to use after your task.
Here's what we need.
2 nodes of m1.xlarge for k8 controllers: 8cpu/16G RAM/160G
4 nodes of m2.xlarge for k8 worker nodes: 8cpu/32G RAM/160G
We deployed and tested our minimal set of ONAP and concluded that we need the resource above.
Former user June 15, 2020 at 6:45 AM
Hi @Former user ,
I sent a mail last week to prepare some cleaning on the Windriver/Intel lab in order to free some resources.
In fact several projects asked for resources releases ago, they are not active anymore but their VMs are still up...
I need to figure out what we can delete and what we cannot before allocating new resources.
Do you have already a rough idea on the amount of resources you need.
I assume it is for a Bell-like deployment so it does not include all the components, if you could provide some dimensioning figures it would be helpful.
I planned to clean the resources end of June, I could give you some feedback once I have a better view.
Please note that I planned to add a windriver/intel lab topic to the agenda of the Integration weekly meeting (https://wiki.onap.org/display/DW/Integration+Project) to address this question. I will also remind the PTL during the PTL meeting today.
Please note that we have a gitlab-runner running on this lab, so it is possible to trigger CI chain, as mentioned by Sylvain, I think it could be an option to create such chain and include the testing and the reporting.
Let's confirm first the resources then see how to build such chain.
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Fix versions
Priority
Medium
Details
Details
Assignee
Reporter
Fix versions
Priority
Medium
Current OOM documentation describes steps to deploy VMs on OPenstack with GUI.
In order to full benefit of Infrastructure as Code, we'd better have Terraform scripts to deploy VMs on Openstack
The scripts will do
1. Create Network and setup subnet, DNS to connect to the Internet
2. Create Security Group to be used by the network and VMs
3. Create VMs for K8s controller nodes and worker nodes