MAAS

Bridging is missing from capability list

Bug #1638575 reported by Andrew McDermott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Gavin Panella
MAAS 2.2.0
2.1
Fix Released
Undecided
Gavin Panella

Bug Description

In Juju we don't want to rely on version numbers - please could we add a feature flag so that we may determine whether bridging is a supported feature.

Related branches

lp://qastaging/~allenap/maas/capabilities-bridging--bug-1638575
Mike Pontillo (community): Approve
Diff: 59 lines (+19/-2)
3 files modified
docs/version.rst (+12/-0)
src/maasserver/api/version.py (+4/-0)
versions.cfg (+3/-2)
lp://qastaging/~allenap/maas/capabilities-bridging--bug-1638575--2.1
Andres Rodriguez (community): Approve
Diff: 59 lines (+19/-2)
3 files modified
docs/version.rst (+12/-0)
src/maasserver/api/version.py (+4/-0)
versions.cfg (+3/-2)
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: Need a capability list to determine what features are supported

IMHO, we need a list of what features we support so that Juju can query MAAS and do auto-determination. We can start with bridging.

summary: - Need a feature flag to determine if bridging is supported
+ Need a capability list to determine what features are supported
Revision history for this message
Gavin Panella (allenap) wrote :

MAAS does publish a capability list already:

  $ curl -s http://server.address:5240/MAAS/api/2.0/version/ | jq
  {
    "version": "2.1.0+bzr5480-0ubuntu1",
    "capabilities": [
      "networks-management",
      "static-ipaddresses",
      "ipv6-deployment-ubuntu",
      "devices-management",
      "storage-deployment-ubuntu",
      "network-deployment-ubuntu"
    ],
    "subversion": "16.04.1"
  }

(The `jq` is just to make the output pretty; it's not required.)

We can add a new flag for bridging.

Gavin Panella (allenap)
summary: - Need a capability list to determine what features are supported
+ Add bridging to published capability list
summary: - Add bridging to published capability list
+ Bridging is missing from capability list
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Andrew McDermott (frobware) wrote : Re: [Bug 1638575] Re: Need a capability list to determine what features are supported

If we could augment the list with bridging, that would be great. Is there
any option in that list which is new to 2.1?

On 2 November 2016 at 17:50, Gavin Panella <email address hidden>
wrote:

> MAAS does publish a capability list already:
>
> $ curl -s http://server.address:5240/MAAS/api/2.0/version/ | jq
> {
> "version": "2.1.0+bzr5480-0ubuntu1",
> "capabilities": [
> "networks-management",
> "static-ipaddresses",
> "ipv6-deployment-ubuntu",
> "devices-management",
> "storage-deployment-ubuntu",
> "network-deployment-ubuntu"
> ],
> "subversion": "16.04.1"
> }
>
> (The `jq` is just to make the output pretty; it's not required.)
>
> We can add a new flag for bridging.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1638575
>
> Title:
> Bridging is missing from capability list
>
> Status in MAAS:
> Triaged
>
> Bug description:
> In Juju we don't want to rely on version numbers - please could we add
> a feature flag so that we may determine whether bridging is a
> supported feature.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1638575/+subscriptions
>

--
Andrew McDermott <email address hidden>
Juju Core Sapphire team <http://juju.ubuntu.com>

Revision history for this message
Gavin Panella (allenap) wrote :

> If we could augment the list with bridging, that would be great. Is
> there any option in that list which is new to 2.1?

That list hasn't changed since 3rd November _2015_, so no :)

Gavin Panella (allenap)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Gavin Panella (allenap)
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
LaMont Jones (lamont) wrote :

The fix was released in maas 2.1.2

Changed in maas:
milestone: none → 2.2.0
Andres Rodriguez (andreserl)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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