#485 OpenNebula Dev instance for "playing around" during duffy development
Closed: Fixed 2 years ago by arrfab. Opened 2 years ago by siddharthvipul1.

In Q4, duffy is an initiative in team community platform engineering with one of the objectives of adding vm/cloud images support (yep, #4).
We would like to work free of any worries of disturbing the primary OpenNebula instance.
Thus, requesting a opennebula instance possibly same as production (making sure playbooks work on all the instances with just changing creds and url)


Metadata Update from @arrfab:
- Issue assigned to arrfab

2 years ago

Metadata Update from @arrfab:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: centos-ci-infra, feature-request, high-gain, medium-trouble

2 years ago

status update : 5 nodes were put aside in inventory (by @siddharthvipul1 ) and so worked with @mobrien today .
The 5 nodes are installed with 8-stream for now.
We've already started working on the infra deploy plan to have the following internal setup :

  • node1 : used as gateway/nat/jump host between CI vlan and internal duffy dev vlan (2 nics)
  • node2 : used for duffy itself, and dhcp/dns/tftp (ansible-role-boot-server)
  • node3 : node to be used for bare-metal reinstall (duffy tests)
  • node 4 and 5 : opennebula cloud setup (controller and compute/hypervisor node)

status update : switch config was applied to isolate node 2-5 in a new internal vlan 50 and node 1 has eth1 added in vlan 50
Ansible role was applied to init nodes like usual and node is a fully functional role for gateway/nat

@siddharthvipul1 : I can find ssh pub keys through fasjson and apply on internal nodes and we can test that later, and give you the needed settings/hops to reach these nodes. We planned to work with Mark today to deploy boot-server role on node 2 (what would become duffy node) and deploy new minimal opennebula setup

Just pushed and applied needed settings so closing this one and I'll just explain to Duffy Team how to get there through irc or google meet meeting

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
CentOS CI Infra Status: Backlog