no separation of instance id from node id

Bug #944325 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

Please forgive the ignorance in opening this bug. I've not taken enough time to research.

I'm given the impression that there is no separation in MaaS between an "instance" and a "node". I'll define these in case my noomenclature is wrong, so you can hopefully figure out what I mean.
 * node: a physical system that used for one deployment, and then re-provisioned for another.
 * Instance: a specific deployment of a node

As I understand it, essentially node == instance.
But if there is no specific entity representing instance, I think it makes some things much more difficult or impossible.

As an example:
 * How many times has node 0x3339 been deployed?
 * Do large machines get used for longer times than small machines?
 * How many total hours has user Bob used?
 * what percentage of the time are our nodes being utilized?

Maybe some of those things can be obtained more difficultly using the current system (as I understand it).

It just seems to me that node and instance are two separate things, and it would be better to model them as such.

Related bugs:
 * bug 1507586: previous owner of node can use oauth creds to retrieve current owner's user-data

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Thanks for the bug Scott. These are all valid comments, but nothing is in scope for the initial release so I'm marking this "low" for now. We can re-visit post-12.04.

Changed in maas:
status: New → Triaged
importance: Undecided → Low
tags: added: tech-debt
Revision history for this message
Scott Moser (smoser) wrote :

Currently, maas has no separation between 'instance' and 'node'. There is no unique information per "instance".

Thus, if I:
  a.) deploy a node
  b.) read oauth credentials from that node
  c.) return that node

I can read the user-data that the new owner provided . user-data might possibly containing sensitive information.

A secondary fallout of this if a node boots into an old installation maas thinks it was deployed and marks it DEPLOYED.

Changed in maas:
milestone: none → 1.9.0
importance: Low → Critical
tags: removed: tech-debt
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This can be fixed without the seperation of instance-id and node-id. We just need to clear the oauth token between each deployment.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I think what you are describing is a different bug then what is document in this bug. If this is really what this bug is about then please update the description and title, because it does not match the issue you just commented about.

Revision history for this message
Mike Pontillo (mpontillo) wrote :

This looks like a feature request. Marking 'wishlist'.

Changed in maas:
importance: Critical → Wishlist
Revision history for this message
Scott Moser (smoser) wrote :
description: updated
Changed in maas:
milestone: 1.9.0 → 2.0.0
Changed in maas:
milestone: 2.0.0 → 2.0.1
milestone: 2.0.1 → 2.1.0
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
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
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.