Hi Kiko, Responses inline.
On Thu, Jun 8, 2017 at 3:20 PM, Christian Robottom Reis <[email protected]> wrote: > Thanks for the summary, these are great! A question: > > On Thu, Jun 08, 2017 at 12:57:58PM -0400, Andres Rodriguez wrote: > > Adding support for ‘upstream’ proxy - MAAS deployed machines will > > continue to use MAAS’ internal proxy, while allowing MAAS ‘ proxy to > > communicate with an upstream proxy. > > Will you allow the option to easily configure MAAS not to use a proxy at > all? There are situations where a proxy is not desireable and I'd like > to ensure we have some flexibility. > This is an option that it is currently available. MAAS can: - Use internal proxy (default). - Use external proxy in non-upstream mode (MAAS & machines will use this proxy directly). - Disable the use of a proxy. Hope this helps. > > > With the continuous improvement of the new MAAS Python Library > > (python-libmaas), we have focused our efforts on the following > improvements > > the past week: > > Ante, what are they key features missing from libmaas for the node > config step for the Foundation work (and is there more we'd like to > have)? I'd like to see if they might make 2.3. > Thanks, > -- > Christian Robottom Reis [+1] 612 888 4935 | [+55] 16 99112 > 6430 > Canonical VP Storage & Automation http://launchpad.net/~kiko > -- Andres Rodriguez Engineering Manager, MAAS Canonical USA, Inc.
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
