Allow disabling nodes in MAAS

Bug #1415112 reported by Jason Hobbs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

I need to be able to test new MAAS releases before putting them into production. So, I need a second MAAS server to test new releases on. I'd like to be able to run both MAAS servers on the same network, so I can test with the same systems I use in production, and so my production systems don't have to change networks (I don't administer the network, just the systems).

With two MAAS systems on the same network I only want one of the MAAS's to respond when a node boots. I'd like to be able to mark nodes as 'disabled' in the production MAAS so that only the staging MAAS server will respond to their PXE requests, and only the secondary MAAS system will issue IPMI commands to power check the nodes.

When I'm done testing on the secondary MAAS, I will either shut it off or mark the nodes on it 'disabled' and reenable them on the production MAAS.

Tags: oil
Changed in maas:
status: New → Triaged
importance: Undecided → Wishlist
Changed in maas:
milestone: none → next
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.