[enhancement] maas-proxy port should be configurable

Bug #1779712 reported by Scott Hussey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Andres Rodriguez
2.3
Fix Released
High
Andres Rodriguez
2.4
Fix Released
High
Andres Rodriguez

Bug Description

When using MAAS as a proxy for joining nodes to access the package repository, the port the proxy listens on is non-configurable and hardcoded to 8000. This should be configurable, preferably via API, but at the very least by a value on the /etc/maas/regiond.conf file.

Related branches

Changed in maas:
milestone: none → 2.5.0
status: New → Triaged
summary: - maas-proxy port should be configurable
+ [enhancement] maas-proxy port should be configurable
tags: added: enhancement
tags: added: wishlist
Changed in maas:
milestone: 2.5.0 → none
Changed in maas:
milestone: none → 2.5.0
importance: Undecided → Medium
assignee: nobody → Andres Rodriguez (andreserl)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Andres Rodriguez (andreserl) wrote :

@Scott,

Master now provides the ability to define the proxy port where the MAAS built-in proxy will be providing services. It will automatically be used for newly deployed machines.

This will be a config option exposed as maas_proxy_port, before we start the backport process, just want to confirm this is what you had in mind.

Thanks.

Changed in maas:
importance: Medium → High
Revision history for this message
Scott Hussey (sh8121) wrote : RE: [Bug 1779712] Re: [enhancement] maas-proxy port should be configurable

Yeah, I think this works great. I'm about to open another one about the syslog log_port parameter for PXE-booting nodes.

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Andres Rodriguez
Sent: Thursday, July 12, 2018 4:38 PM
To: HUSSEY, SCOTT T <email address hidden>
Subject: [Bug 1779712] Re: [enhancement] maas-proxy port should be configurable

@Scott,

Master now provides the ability to define the proxy port where the MAAS built-in proxy will be providing services. It will automatically be used for newly deployed machines.

This will be a config option exposed as maas_proxy_port, before we start the backport process, just want to confirm this is what you had in mind.

Thanks.

--
You received this bug notification because you are subscribed to the bug report.
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1779712&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=pLHoqiMCyKl-sAGs-ZeWsw&m=GmF_ppYYa7augRSRUqeq-MPo08SOf86mPRjiiuM95Ao&s=w8v7Iwtw8zcDtKe1XiS8siNuPKF-RJjQ8Bpwg8YlDg4&e=

Title:
  [enhancement] maas-proxy port should be configurable

Status in MAAS:
  Fix Committed
Status in MAAS 2.4 series:
  Triaged

Bug description:
  When using MAAS as a proxy for joining nodes to access the package
  repository, the port the proxy listens on is non-configurable and
  hardcoded to 8000. This should be configurable, preferably via API,
  but at the very least by a value on the /etc/maas/regiond.conf file.

To manage notifications about this bug go to:
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_maas_-2Bbug_1779712_-2Bsubscriptions&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=pLHoqiMCyKl-sAGs-ZeWsw&m=GmF_ppYYa7augRSRUqeq-MPo08SOf86mPRjiiuM95Ao&s=FhpCaHutp2FjTlkj5YfHuaKikYCaIzwr19HFURfluJA&e=

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear all,

MAAS 2.3.4 and MAAS 2.4.1 will contain this new option available only over the API. An example on how to set it is:

maas <user> maas set-config name=maas_proxy_port value=9000

MAAS 2.3.4, 2.4.1 are currently under testing before release. Once released we will make the proper announcements!

Thanks

Changed in maas:
milestone: 2.5.0 → 2.5.0alpha1
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Scott Hussey (sh8121) wrote :

This looks good, thank you.

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.