I missed this one @Wei Zhou <[email protected]> , but yes, I like your approach, and have afaik already commented there. Good stuff!
Andrija Panić openvddk.com · v2kmigrate.com On Mon, Oct 5, 2026 at 10:44 AM Wei ZHOU <[email protected]> wrote: > Hi Andrija, > > I don't think the default choice is important here. Whenever a user creates > an isolated network, they can select the network offering they want from > the list. > > In my opinion, this is a better approach than having a network offering > with the same name behave differently across different CloudStack versions > or environments, especially between upgraded and fresh installations. > Keeping the behaviour consistent would be less confusing for users and > operators. I also created another PR with a new network offering for this > approach: https://github.com/apache/cloudstack/pull/14286 > > > Kind regards, > Wei > > > > > On Fri, Oct 2, 2026 at 6:16 PM Andrija Panic <[email protected]> > wrote: > > > missed this one, sorry.... > > > > We can, but the point is that it becomes a default one. > > What does a new operator/ACS user knows... - which means identical > > behaviour (give or take) as the PR itself. > > > > > > On Wed, Sep 16, 2026 at 9:21 AM Wei ZHOU <[email protected]> wrote: > > > > > Hi Andrija, > > > > > > Just a thought: could we introduce a new network offering with the > > default > > > egress policy set to true? > > > > > > This would avoid breaking backwards compatibility or causing unexpected > > > changes for existing users, while still providing a new option for > users > > > who prefer the default ALLOW behavior. > > > > > > > > > > > > Kind regards, > > > > > > Wei > > > > > >
